aws s3 bucket needs to match the domain for website hosting.
let's say if apple uses s3, they need to create bucket name "apple.com", and then we can find what aws account which apple is using.
let's say if apple uses s3, they need to create bucket name "apple.com", and then we can find what aws account which apple is using.
I have dozens of s3 static websites served from a single s3 bucket, all with unique top-level domains, each in its own folder within that single bucket - much easier this way.
Given anyone can create a bucket with any name (if its not already in use), you can't count on getting the bucket name that matches your domain name.
This is outdated information, and not required anymore when using CloudFront.
And even in the past, you could use the S3 API to implement a reverse proxy without matching bucket and domain names.
https://docs.aws.amazon.com/AmazonS3/latest/userguide/websit...