3 ms·

Please don't do this. I've used S3 to host static web pages and adding an additional service would add complexity and cost. Also, I'll point out that even a cou

Please don't do this. I've used S3 to host static web pages and adding an additional service would add complexity and cost. Also, I'll point out that even a couple of years ago, AWS made it rather uncomfortable for me to expose pages to the public. IIRC, each time I changed the html, I needed to also remind AWS that I wanted the file public.

x3n0ph3n3 4y ago
Just put CloudFront in front of it. Then you get to use your own domain.
- master_crab 4y ago
  You dont need Cloudfront to use your own domain. You can do it with buckets alone too, but they have to follow a clear naming policy.
  - x3n0ph3n3 4y ago
    You do if you want HTTPS... > Amazon S3 does not support HTTPS access to the website. If you want to use HTTPS, you can use Amazon CloudFront to serve a static website hosted on Amazon S3.
- laserlight 4y ago
  Using your own domain doesn't require CloudFront [0]. [0] https://docs.aws.amazon.com/AmazonS3/latest/userguide/website-hosting-custom-domain-walkthrough.html https://docs.aws.amazon.com/AmazonS3/latest/userguide/websit...
  - x3n0ph3n3 4y ago
    It does if you want HTTPS. > Amazon S3 does not support HTTPS access to the website. If you want to use HTTPS, you can use Amazon CloudFront to serve a static website hosted on Amazon S3.