// Add steps as necessary for accessing the software, post-configuration, and testing. Don’t include full usage instructions for your software, but add links to your product documentation for that information.
//Should any sections not be applicable, remove them

== Test the deployment
// If steps are required to test the deployment, add them here. If not, remove the heading

=== Snyk integration with Amazon ECR
. Log in to your Snyk account.
. Go to *Projects*,  select *Add projects*, and then select *Amazon ECR*.
. Select single or multiple images.
. Select *Add selected repositories*.

For more information, see https://support.snyk.io/hc/en-us/articles/360003947077-Amazon-Elastic-Container-Registry-ECR-add-images-to-Snyk[Amazon Elastic Container Registry (ECR): add images to Snyk^].

=== Snyk integration with AWS Lambda
. Log in to your Snyk account.
. Go to *Projects*, select *Add projects*, and then select *AWS Lambda*.
. Select the relevant functions.
. Select *Add selected functions*.

NOTE: Snyk currently supports integration with AWS Lambda for Node, Ruby, and Java projects.

For more information, see https://support.snyk.io/hc/en-us/articles/360004002418-AWS-Lambda-integration[AWS Lambda integration^].

// == Post-deployment steps
// If post-deployment steps are required, add them here. If not, remove the heading

// == Best practices for using {partner-product-short-name} on AWS
// Provide post-deployment best practices for using the technology on AWS, including considerations such as migrating data, backups, ensuring high performance, high availability, etc. Link to software documentation for detailed information.

// _Add any best practices for using the software._

// == Security
// Provide post-deployment best practices for using the technology on AWS, including considerations such as migrating data, backups, ensuring high performance, high availability, etc. Link to software documentation for detailed information.

// _Add any security-related information._

// == Other useful information
//Provide any other information of interest to users, especially focusing on areas where AWS or cloud usage differs from on-premises usage.

//Add any other details that will help the customer use the software on AWS.
