You decide to configure a bucket for static website hosting. As per the AWS documentation, you create a bucket named `mybucket.com`. You also enable website hosting with an index document of `index.html` and leave the error document as blank. You then upload a file named `index.html` to the bucket. After clicking on the endpoint of mybucket.com.s3-website-us-east-1.amazonaws.com you receive 403 Forbidden error. You then change the CORS configuration on the bucket so that everyone has access. However, you still receive the 403 Forbidden error. What additional step do you need to do so that the endpoint is accessible to everyone?

Answer options:

A.Register mybucket.com on Route53
B.Wait for the DNS change to propagate
C.You need to add a name for the error document, because it is a required field
D.Change the permissions on the index.html file also, so that everyone has access

Answer – D
You are receiving the 403 Forbidden Error because you do not have the permissions to view the index.html file.
Option A is incorrect because this is an S3 hosted website. Route 53 does not come into the picture.
Option B is incorrect because it is a static website hosted on S3. This issue is not related to DNS resolution.
Option C is incorrect. Even if you add the error document, you will get the error because you need to set the proper permissions.
Option D is CORRECT because it sets the appropriate permissions so that the user has access to the index.html.
For more information on web site hosting in S3, please visit the below link:
http://docs.aws.amazon.com/AmazonS3/latest/dev/WebsiteHosting.html
Note:
The question is referring to Configuring a bucket for Website Hosting. In this scenario, Route53 is not required. However, extra configuration in S3 is needed other than making it public.
For more information, please refer to:
https://docs.aws.amazon.com/AmazonS3/latest/dev/IndexDocumentSupport.html