4 ms·

> The name of the bucket used for Transfer Acceleration must be DNS-compliant and must not contain periods ("."). Source: http://docs.aws.amazon.com/AmazonS3/l

> The name of the bucket used for Transfer Acceleration must be DNS-compliant and must not contain periods ("."). Source: http://docs.aws.amazon.com/AmazonS3/latest/dev/transfer-acceleration.html#transfer-acceleration-getting-started http://docs.aws.amazon.com/AmazonS3/latest/dev/transfer-acce... > The bucket names must match the names of the website that you are hosting. For example, to host your example.com website on Amazon S3, you would create a bucket named example.com. Source: http://docs.aws.amazon.com/AmazonS3/latest/dev/website-hosting-custom-domain-walkthrough.html http://docs.aws.amazon.com/AmazonS3/latest/dev/website-hosti... ... Looks like they don't want you replacing CloudFront with Amazon S3 Transfer Acceleration - which is a royal pain for some of my use cases (internal facing websites that don't need a full CDN).

re 11y ago
S3 Website Hosting is distinct from CloudFront; you can create a CloudFront distribution backed by a bucket with any name. You can combine the two, but it isn't required. http://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/MigrateS3ToCloudFront.html http://docs.aws.amazon.com/AmazonCloudFront/latest/Developer... http://docs.aws.amazon.com/gettingstarted/latest/swh/website-hosting-intro.html http://docs.aws.amazon.com/gettingstarted/latest/swh/website...
EwanToo 11y ago
I think it's simply wildcard SSL getting in the way, if you put a . in the bucket name, the DNS record becomes a.b.c.s3-xxxx.amazonaws.com The wildcard SSL certificate they use only matches the c.s3-xxxx.amazonaws.com part of the sub domain