4 ms·
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
by tuananh 3y ago
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.
- ejb999 3y agoNot exactly - they Can do that, but they don't need to match - using cloudfront in front of your s3 website and then the site can be served from any bucket or folder within a bucket. 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.
- tuananh 3y agoah thanks. iirc it used to be like that ( when use without cloudfront).
- mayank 3y ago> aws s3 bucket needs to match the domain for website hosting. 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.
- hacker_newz 3y agoThat is not how s3 buckets work.
- tuananh 3y agoit used to be like that (without cloudfront) https://docs.aws.amazon.com/AmazonS3/latest/userguide/website-hosting-custom-domain-walkthrough.html https://docs.aws.amazon.com/AmazonS3/latest/userguide/websit...