A temporary public static website is hosted in Amazon S3. A bucket was created with default settings, static website hosting enabled, and index.html and error.html objects uploaded. Accessing the website URL returns HTTP 403 Forbidden (Access Denied). What should the SysOps administrator do to fix this?

The correct solution addresses two common S3 website access issues. First, by default, S3 Block Public Access settings prevent public access to buckets and objects, causing the 403 Forbidden error. Disabling these settings is necessary for a public website. Second, even after disabling block public access, explicit permissions are required. A bucket policy granting s3:GetObject permission to (all objects) allows anonymous users to retrieve the website content. Creating a Route 53 DNS record is for domain mapping, not for resolving access denied errors. Changing object ACLs is an older method and less scalable than a bucket policy, and often insufficient if Block Public Access is still enabled. Granting s3:PutObject permission would allow users to upload objects, which is a security risk and not required for viewing a static website.