AWS marketplace documentation change
Summary
Clarified that the 'Test Add version' option validates AMI scanning without publishing a new version, and specified AMI-based product requirements
Security assessment
The changes clarify workflow steps and scanning validation but do not address a specific security vulnerability or introduce new security documentation. The mention of scanning success relates to existing security processes without evidence of addressing a new issue.
Diff
diff --git a/marketplace/latest/userguide/best-practices-for-building-your-amis.md b/marketplace/latest/userguide/best-practices-for-building-your-amis.md index 124e1e194..f1ab35ab0 100644 --- a//marketplace/latest/userguide/best-practices-for-building-your-amis.md +++ b//marketplace/latest/userguide/best-practices-for-building-your-amis.md @@ -145 +145 @@ This option is available for sellers who have already created an AMI product. Le - 2. Select your product from **Server products**. + 2. Select your product from **Server products**. This must be an AMI-based product. The product can be in any state and does not need to be in the **Public** published state for next steps. @@ -149 +149 @@ This option is available for sellers who have already created an AMI product. Le - 4. Select **Test ‘Add version’**. + 4. Select **Test ‘Add version’**. Follow the prompts to submit a request with your AMI details. If the request succeeds, this indicates that the AMI has passed scanning successfully. Unlike the **Add new version** option, **Test 'add version'** does not add a new version to the AMI-based product if the scan is successful.