
Ultimate access to all questions.
A developer has deployed a static website's assets to an Amazon S3 bucket and is using Amazon CloudFront with origin access control for distribution. Users can access specific pages but encounter errors when trying to access directories without a file name, such as '/products/'. The developer must enable directory access without specifying a file name and without making the S3 bucket public. What is the appropriate solution?
A
Modify CloudFront settings to use 'index.html' as the default object for the root.
B
Enable static website hosting on the S3 bucket, set 'index.html' as the index document, adjust the bucket policy for access, and update CloudFront's origin to the S3 website endpoint.
C
Implement a CloudFront function to automatically append 'index.html' to directory requests and integrate it into the distribution's behavior.
D
Configure a custom error response in CloudFront to redirect HTTP 404 errors to '/index.html' with an HTTP 200 status.