AWS introduced account-regional namespaces for S3, fixing global bucket name collisions that broke IaC automation for 18 years. New format: {prefix}-{account-id}-{region}-an. CloudFormation gets the B

InfoQ is a leading online platform for software developers, architects, and technical leaders, providing news, articles, presentations, and interviews on a wide range of topics, including agile practices, DevOps, microservices, and emerging technologies. With a focus on quality content and expert insights, InfoQ helps professionals stay informed about the latest trends, best practices, and industry developments. Developers can learn from real-world experiences, gain  knowledge, and connect with peers in the global software community through InfoQ's diverse and engaging content.

InfoQ

AWS has introduced account-regional namespaces for S3 general-purpose buckets, resolving an 18-year limitation where bucket names existed in a single global namespace. Buckets now follow the format {prefix}-{account-id}-{region}-an, scoping names to a specific AWS account and region. This eliminates BucketAlreadyExists errors in IaC pipelines, simplifies CloudFormation templates via a new BucketNamePrefix property, and adds an IAM condition key (s3:x-amz-bucket-namespace) for policy enforcement. The change also mitigates confused-deputy security attacks by making bucket names unpredictable without the account ID. The feature is opt-in, backward-compatible, available in 35 regions at no extra cost, and mirrors scoping approaches long used by Azure and Google Cloud.

AWS S3 Introduces Account-Regional Namespaces, Ending 18 Years of Global Bucket Name Collisions