BucketAlreadyExists: The requested bucket name is not available
S3 bucket names are global across all AWS accounts, and someone else already uses this one.
The requested bucket name is not availableYour previous request to create the named bucket succeeded and you already own it Meaning
BucketAlreadyExists means another account owns the name; BucketAlreadyOwnedByYou means you already created it (often in IaC re-runs). Deleted bucket names can take time to become available again.
Common causes
- Name taken by another AWS account
- You already own the bucket (BucketAlreadyOwnedByYou)
- Recently deleted bucket name not yet released
⚡ Quick fix
- Choose a unique name (add account ID/region/random suffix)
- Import the existing bucket into Terraform/CloudFormation instead of creating it
- Treat BucketAlreadyOwnedByYou as success in scripts
Detailed fix by platform
AWS CLI
aws s3api create-bucket --bucket myapp-assets-123456789012-euw1 --region eu-west-1 --create-bucket-configuration LocationConstraint=eu-west-1
How to diagnose
- Owner — aws s3api head-bucket --bucket name (403 = someone else, 200 = yours)
- IaC — Bucket created outside the stack?
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
Most viewed in AWS
Other ways to find it
Where this error sits
Origin: Platform & cloud. Errors that are often confused with or caused by this one (click to open):
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
💬 What worked for others
No tips yet — did something else fix this for you?
Share what worked for you
Tips are checked by an editor before they appear. Links are removed.
Report a correction or suggest an improvement
Last updated 13 Oct 2026