CODEWITHSUNDEEP
amazon-web-servicesamazon-s3amazon-route53
fredley
fredley

Reputation: 33931

Code: NoSuchBucket

So I've followed the instructions in this excellent guide for setting up a redirect from sub.my-domain.com to my-domain.com/sub. I've checked and double checked my settings, but when I access sub.my-domain.com I get the error

404 Not Found

Code: NoSuchBucket
Message: The specified bucket does not exist
BucketName: sub.my-domain.com

If I go to sub.s3-website-eu-west-1.amazonaws.com (the bucket I created) it is redirected correctly, and I am 100% certain double-plus confirmed that the url in the CNAME Record Set is the correct one. What is going on?

It seems like BucketName in the error message is wrong, but why is this?

Upvotes: 32

Views: 75169

Answers (3)

Oleksandr Hrin
Oleksandr Hrin

Reputation: 896

in my case

Code: NoSuchBucket

appeared because I tried to use js s3-client to copy folder from S3 bucket to other S3 bucket, instead of copying file and it doesn't support copying folders, that error message is very missleading!

Upvotes: 0

Adam Gawne-Cain
Adam Gawne-Cain

Reputation: 1710

You can fix it by renaming your bucket as "Michael - sqlbot" says.

But if you really want to keep your bucket name, then you can use CloudFront to forward requests to your existing bucket, and then use DNS to map the website name(s) to the CloudFront name.

CloudFront is another Amazon Web Service that caches HTTP requests to your bucket in caches all around the world, so your website will be faster :-). But you will have to pay more :-(.

Upvotes: 2

Michael - sqlbot
Michael - sqlbot

Reputation: 179364

It's hard to tell since you (sensibly) obfuscated your question but the way you've written it, I think this is a case of not naming the bucket correctly for this application.

sub.s3-website-eu-west-1.amazonaws.com

If the web site is "sub.example.com," then that's not the correct convention, so I wonder if your bucket name is also not correct: the bucket should be named "sub.example.com" -- not "sub" -- and the web site endpoint should be sub.example.com.s3-website-eu-west-1.amazonaws.com.

Upvotes: 60

Related Questions