A static website is hosted in an S3 bucket with static website hosting enabled and objects uploaded, but accessing the site returns 403 Forbidden - Access Denied. What modification will resolve the error?

The correct solution is to attach a bucket policy that grants public read permission specifically to the objects in the bucket. When hosting a static website on Amazon S3, the objects (website files) must be publicly readable for browsers to access them. A bucket policy is the standard way to grant this permission. Attaching a bucket policy that grants public read permission to the bucket itself is insufficient because permissions are applied to objects, not just the bucket container. Deleting a default bucket policy that explicitly denies read access is unlikely to be the issue, as S3 buckets are private by default and require explicit public access. Enabling CORS (Cross-Origin Resource Sharing) is used for allowing resources from one domain to be accessed by a script from another domain, not for resolving initial 403 Forbidden errors for direct object access.