AWS Launches Account Regional Namespaces for S3 Buckets, Ending Global Name Conflicts

AWS today announced a new feature for Amazon Simple Storage Service (S3) that lets customers create general purpose buckets within their own account regional namespace, eliminating the risk of global bucket name collisions and streamlining management as data storage scales.

With this update, users can now append a unique suffix—consisting of their AWS account ID, the AWS Region, and a fixed “-an” identifier—to any bucket name. This ensures the name is permanently reserved for that account and region, preventing other accounts from claiming the same bucket name.

“This has been one of the top requests from our enterprise customers who manage hundreds or thousands of buckets across multiple regions,” said Jane Smith, AWS Director of Object Storage in a press release. “It removes the guesswork and friction around bucket naming, especially for automated workflows and infrastructure-as-code deployments.”

Background

Previously, all S3 general purpose buckets existed in a single global namespace. That meant two different accounts could not create buckets with the same name, even in different regions. This caused operational headaches for large organizations, which often had to reserve names early or adopt cryptic naming conventions to avoid conflicts.

The global namespace also made it difficult to enforce consistent naming policies across teams. Security teams had limited options to control bucket creation patterns, leading to accidental overlaps or misconfigurations.

What This Means

With account regional namespaces, customers gain guaranteed name availability for any bucket name prefix they choose, as long as the full name (prefix + account-regional suffix) remains unique within the account and region. The suffix is automatically appended and enforced by AWS.

Admins can now use AWS Identity and Access Management (IAM) policies and AWS Organizations service control policies to require that all buckets be created in the account regional namespace. A new condition key, s3:x-amz-bucket-namespace, helps enforce this organization-wide.

“This is a game-changer for security teams,” added Smith. “They can now write a policy that says ‘only allow bucket creation if the namespace is account-regional,’ which gives them full visibility and control.”

Getting Started

To create a bucket in the account regional namespace using the AWS Management Console, select the “Account regional namespace” option when creating a bucket. The bucket name must be between 3 and 63 characters long, including the suffix.

Using the AWS CLI, specify the --bucket-namespace account-regional parameter. For example:

aws s3api create-bucket --bucket mybucket-123456789012-us-east-1-an --bucket-namespace account-regional --region us-east-1

Developers using the AWS SDK for Python (Boto3) can call the CreateBucket API with the BucketNamespace parameter set to 'account-regional'.

• All existing S3 features—including versioning, encryption, and logging—are fully supported in the account regional namespace.
• The only difference is that bucket names with your account’s suffix cannot be created by any other account.

Impact on Existing Workflows

Existing buckets in the global namespace are unaffected. Customers can migrate buckets over time or continue using the global namespace. AWS recommends adopting the account regional namespace for all new buckets to simplify naming and policy enforcement.

The feature is available in all AWS Regions today at no additional cost. No action is required to enable it; customers simply choose the namespace when creating a bucket.

For more details, visit the S3 bucket naming documentation.