How do I troubleshoot issues when I try to create an Amazon S3 bucket?

Resolution

You might get one of the following errors when you try to create an Amazon S3 bucket:

• "A conflicting conditional operation is currently in progress against this resource"
• "TooManyBuckets: You have attempted to create more buckets than allowed"
• "Access Denied"
• "BucketAlreadyExists"
• "Networking Error"
• "InvalidBucketName"

Note: If you receive errors when you run AWS Command Line Interface (AWS CLI) commands, then see Troubleshooting errors for the AWS CLI. Also, make sure that you're using the most recent AWS CLI version.

"A conflicting conditional operation is currently in progress against this resource"

This error occurs for the following reasons:

• You tried to create a bucket with the same name as a bucket that you recently deleted.
• You tried to create a bucket with the same name at the same time as someone else or another AWS Identity and Access Management (IAM) identity.

Because bucket names must be globally unique, you can't have two buckets with the same name. After you delete a bucket, wait a few hours for the changes to take effect across all AWS Regions. In most cases, you can create a bucket a few hours after you deleted the previous bucket. However, it might take 48–72 hours for the changes to take effect. It's a best practice to wait at least 48 hours to create the S3 bucket again.

For more information, see Why do I get the error "A conflicting conditional operation is currently in progress against this resource" from Amazon S3 when I recreate a bucket?

"TooManyBuckets: You have attempted to create more buckets than allowed"

This error occurs when you try to create multiple buckets and exceed the bucket quota for your AWS account. By default, Amazon S3 has a soft quota of 10,000 buckets. If you require additional buckets, then you can request a service quota increase to increase your bucket quota to a maximum of 1 million buckets. 

"Access Denied"

To create an S3 bucket, you must have CreateBucket permission for the IAM entity that tried to create the bucket. If you use service control policies (SCPs), then make sure that they don't explicitly deny the CreateBucket permission.

"BucketAlreadyExists"

Amazon S3 bucket names must be unique across all accounts in all Regions within a partition. When you get the error "Bucket name already exists" or "BucketAlreadyExists", another account owns an S3 bucket with the same name. To resolve this issue, use a different bucket name when you create the s3 bucket. 

Review the existing buckets on the Amazon S3 console. Or, run the head-bucket AWS CLI command to confirm whether you already have a bucket with the same name.

"Networking Error"

To resolve this error, take the following actions:

• Check your browser for proxy server settings or browser extensions that you turned on.
• Clear the cache and cookies on your browser.
• Try a different browser to determine whether the issue persists across browsers.
• Use incognito mode in your web browser to access the Amazon S3 console.
• If you still experience issues, then run the AWS CLI command create-bucket to create the bucket:

aws s3api create-bucket --bucket my-bucket --region your-region

Note: Replace your-region with your Region.

"InvalidBucketName"

This error occurs when the bucket name that you tried to create isn't valid. To resolve this issue, make sure that you follow the general purpose bucket naming rules.

Related information

Error responses