•1 min read•from InfoQ
AWS S3 Introduces Account-Regional Namespaces, Ending 18 Years of Global Bucket Name Collisions
Our take
AWS has introduced account-regional namespaces for S3, effectively eliminating global bucket name collisions that have hindered Infrastructure as Code (IaC) automation for 18 years. This new naming format, which incorporates a prefix, account ID, and region, enhances predictability and security. Additionally, CloudFormation now features the BucketNamePrefix property, while IAM includes the s3:x-amz-bucket-namespace condition key, which helps prevent confused-deputy attacks. This progressive update empowers users to navigate their data management more effectively, ensuring a smoother and more secure experience.
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 BucketNamePrefix property, and IAM gets the s3:x-amz-bucket-namespace condition key. Prevents confused-deputy attacks by making names unpredictable when there is no account ID.
By Steef-Jan WiggersRead on the original site
Open the publisher's page for the full experience