A small business wants to host a static marketing site (HTML, CSS, and images) directly from an S3 bucket, serving the content over plain HTTP to anyone on the internet. Which configuration is required, at minimum, to make this work?
- Enable static website hosting on the bucket, specify an index document, and allow public read access to the objects
- Enable S3 Transfer Acceleration on the bucket so the site loads faster worldwide
- Turn on S3 Object Lock so visitors cannot delete pages
- Enable S3 Intelligent-Tiering so page assets automatically move between access tiers
Why A? And why not the others?
Correct answer: A. Enable static website hosting on the bucket, specify an index document, and allow public read access to the objects
Static website hosting on S3 requires enabling the website hosting configuration on the bucket, specifying at least an index document, and making the objects publicly readable, since S3 buckets and objects are private by default. All of this is necessary: without public read access, visitors receive access-denied errors even with hosting enabled, and without an index document configured, requests to the bucket root have nothing to serve. Transfer Acceleration only affects the speed of uploads and downloads over long distances using CloudFront edge locations; it has no bearing on whether a site can be served at all and is unrelated to public HTTP hosting. Object Lock protects objects from deletion or overwrite for compliance purposes and would have no effect on visitors being able to view the marketing pages. Intelligent-Tiering only moves objects between S3 access tiers based on access patterns to save cost; it does not enable public web serving.
Source: AWS S3 docs: Hosting a static website using Amazon S3