CODEWITHSUNDEEP
amazon-web-servicesamazon-s3
gianni
gianni

Reputation: 1347

AWS S3 Bucket name already exists

I know this question has been asked before, but replies didn't really help my case. I am trying to create a bucket in S3 and I always receive the 'Bucket name already exists' error. I tried any possible combination but no luck, also the format is compliant to the docs.

Any idea of what I am doing wrong?

Thanks

enter image description here

Upvotes: 23

Views: 27852

Answers (5)

Raj Bhinde
Raj Bhinde

Reputation: 1

Was facing the same issue irrespective of the name I give. Issue from my end was that time on my laptop was not in sync, once I synced it from date and time settings in windows, I was able to create the s3 bucket

Upvotes: 0

Robbie
Robbie

Reputation: 76

S3 buckets require a globally unique name. The reason it's saying it already exists, is because another user account in AWS already used "t1-bucket' to name their S3.

One thing you can do is come up with your own naming convention. If you have a company, maybe use that to name your resources. For example "t1-bucket-myCompany" If you aren't using AWS for a company, try your name or initials.

Upvotes: 4

Mickers
Mickers

Reputation: 1449

I had this exact same problem. I am the sole user/owner of my aws account and I keep getting this message. There is exactly 1 bucket on my account which was created from an example project I've already forgotten about. I was attempting to add a bucket named "t1-bucket" and I'm being told over and over that it already exists. I know this not to be false so I tried doing the same thing using edge instead of chrome and got the exact same error. I changed the name to "t1-bucket-force" and it worked...

I don't want to imply adding "-force" actually forced anything.

I think there's something going on with the name enforcement rules that aws is not telling us: "Bucket name must be between 3 and 63 characters long".

Upvotes: 1

gianni
gianni

Reputation: 1347

So, I finally solved my issue.

As I stated in the description of my question, my problem was not the formatting or the validity of the bucket name, the name was also unique and not used. Weirdly enough, I could not create the bucket when signed in using Chrome, but I succeeded doing it using Edge.

One note for the happy down-voters: maybe you can share some of your wisdom explaining the reason for down-voting, so we can all learn from it.

Upvotes: 20

Sager Gulabani
Sager Gulabani

Reputation: 356

According to the AWS docs:

An Amazon S3 bucket name is globally unique, and the namespace is shared by all AWS accounts. This means that after a bucket is created, the name of that bucket cannot be used by another AWS account in any AWS Region until the bucket is deleted.

Someone else has already created a bucket with this name.

Upvotes: 22

Related Questions