AWS AWSEC2 documentation change
Summary
Added documentation for new AMI security features: usage reports, references, and AmazonEC2ImageReferencesAccessPolicy
Security assessment
Documents new security-focused capabilities for AMI management including usage tracking and a managed policy for scanning AMI references, improving security visibility but not fixing a specific vulnerability.
Diff
diff --git a/AWSEC2/latest/UserGuide/DocumentHistory.md b/AWSEC2/latest/UserGuide/DocumentHistory.md index afd02866c..f22177b15 100644 --- a//AWSEC2/latest/UserGuide/DocumentHistory.md +++ b//AWSEC2/latest/UserGuide/DocumentHistory.md @@ -12,0 +13,3 @@ Change| Description| Date +[AmazonEC2ImageReferencesAccessPolicy – new managed policy](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/security-iam-awsmanpol.html#security-iam-awsmanpol-AmazonEC2ImageReferencesAccessPolicy.html)| Amazon EC2 added the AmazonEC2ImageReferencesAccessPolicy managed policy to provide permission to scan all resources types supported by the EC2 DescribeImageReferences API.| August 26, 2025 +[AMI usage reports](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/your-ec2-ami-usage.html)| If you share your Amazon Machine Images (AMIs) with other AWS accounts—whether with specific AWS accounts, organizations, organizational units (OUs), or publicly—you can see how these AMIs are used by creating AMI usage reports. The reports provide visibility into which AWS accounts are using your AMIs in EC2 instances or launch templates, and how many instances or launch templates are referencing each AMI.| August 26, 2025 +[AMI references](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-ami-references.html)| You can identify your AWS resources that reference specified Amazon Machine Images (AMIs), regardless of whether the AMIs are public or private, or who owns them. This visibility helps you ensure your resources use the latest compliant AMIs.| August 26, 2025