AWS AWSEC2: Add S3-backed AMI registration deprecation notice
Summary
Adds an Important note that starting November 2, 2026, accounts without an existing Amazon S3-backed AMI in a Region can no longer register a new one there, and recommends Amazon EBS-backed AMIs.
Security assessment
A deprecation/lifecycle notice for instance-store backed AMI registration; it contains no vulnerability reference, credential, encryption, or access-control guidance.
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 register a new one in that Region. If your account already owns an Amazon S3-backed AMI in a Region, you can continue to register 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/creating-an-ami-instance-store.md b/AWSEC2/latest/UserGuide/creating-an-ami-instance-store.md index edcc1b6..a46ba1b 100644 --- a//AWSEC2/latest/UserGuide/creating-an-ami-instance-store.md +++ b//AWSEC2/latest/UserGuide/creating-an-ami-instance-store.md @@ -18,0 +19,4 @@ You can't create an Amazon S3-backed Windows AMI because Windows AMIs don't supp +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 register a new one in that Region. If your account already owns an Amazon S3-backed AMI in a Region, you can continue to register 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). + +###### Important +