Code: NoSuchBucket

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 :-(.

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.