AWS AWSEC2: Add S3-backed AMI creation deprecation notice
Summary
Adds an Important note stating that starting November 2, 2026, accounts that do not already own an Amazon S3-backed AMI in a Region can no longer create one there, and recommends using Amazon EBS-backed AMIs.
Security assessment
This is a lifecycle/deprecation announcement for a legacy AMI storage type, not a security advisory; it references no CVE and describes no vulnerability or security control.
Evidence
+Starting November 2, 2026, if your AWS account doesn't already own an Amazon S3-backed AMI in an AWS Region, you can no longer create a new one in that Region. If your account already owns an Amazon S3-backed AMI in a Region, you can continue to create Amazon S3-backed AMIs in that Region. AWS recommends using Amazon EBS-backed AMIs. For more information, see [Create an Amazon EBS-backed AMI](./creating-an-ami-ebs.html).
Diff
diff --git a/AWSEC2/latest/UserGuide/ComponentsAMIs.md b/AWSEC2/latest/UserGuide/ComponentsAMIs.md index d421c3a..cef086b 100644 --- a//AWSEC2/latest/UserGuide/ComponentsAMIs.md +++ b//AWSEC2/latest/UserGuide/ComponentsAMIs.md @@ -56,0 +57,4 @@ Amazon S3-backed AMIs are considered end of life and are not recommended for new +###### Important + +Starting November 2, 2026, if your AWS account doesn't already own an Amazon S3-backed AMI in an AWS Region, you can no longer create a new one in that Region. If your account already owns an Amazon S3-backed AMI in a Region, you can continue to create Amazon S3-backed AMIs in that Region. AWS recommends using Amazon EBS-backed AMIs. For more information, see [Create an Amazon EBS-backed AMI](./creating-an-ami-ebs.html). +