Static website hosting on S3 in AWS - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is Amazon S3 used for in static website hosting?

Amazon S3 stores your website files like HTML, CSS, and images, and serves them directly to visitors without needing a server.

beginner

How do you enable static website hosting on an S3 bucket?

You go to the bucket properties, find the 'Static website hosting' section, and enable it by specifying an index document like 'index.html'.

intermediate

Why do you need to set bucket policy or object permissions for static website hosting?

Because by default, S3 buckets are private. You must allow public read access so visitors can see your website files.

beginner

What is the purpose of the index document in S3 static website hosting?

The index document is the default page shown when someone visits your website root, usually 'index.html'.

intermediate

Can you use custom domain names with S3 static website hosting?

Yes, by using Amazon Route 53 or another DNS service to point your domain to the S3 website endpoint.

What type of content is best suited for hosting on Amazon S3 static website hosting?

A Static files like HTML, CSS, and images

B Dynamic web applications with server-side code

C Databases and backend services

D Streaming video content

Amazon S3 static website hosting is designed to serve static files such as HTML, CSS, and images directly to users.

Which setting must be enabled in an S3 bucket to serve a static website?

A Static website hosting

B Versioning

C Cross-region replication

D Server access logging

Static website hosting must be enabled in the bucket properties to serve website content.

What permission is essential for users to access your static website files on S3?

A Full control to all users

B Write access

C Public read access

D No permissions needed

Public read access allows anyone to view the website files stored in the bucket.

What is the default document called that S3 serves when a user visits your website root?

A main.html

B default.html

C home.html

D index.html

The index document is usually named 'index.html' and is the default page served.

How can you use your own domain name with an S3 static website?

A By uploading a certificate to S3

B By configuring DNS to point to the S3 website endpoint

C By enabling versioning on the bucket

D By enabling server-side encryption

You configure your domain's DNS to point to the S3 website endpoint to use a custom domain.

Explain the steps to host a static website on Amazon S3.

Think about what you need to make your files visible and accessible on the internet.

Describe how to make your S3 static website accessible using a custom domain name.

Consider how domain names connect to website hosting services.

Practice

1. What is the first step to host a static website on AWS S3?

easy

A. Set up a database

B. Upload files to EC2

C. Configure a Lambda function

D. Create an S3 bucket

Solution

1. Step 1: Understand the hosting process

   Hosting a static website on S3 starts by creating a storage space called a bucket.

2. Step 2: Identify the correct initial action

   Before uploading files or configuring anything else, you must create the bucket to hold your website files.

3. Final Answer:

   Create an S3 bucket -> Option D

4. Quick Check:

   First step = Create bucket [OK]

Hint: Start by making a bucket to hold your website files [OK]

Common Mistakes:

• Trying to upload files before creating a bucket
• Confusing S3 with EC2 for hosting
• Setting up Lambda or database unnecessarily

2. Which of the following is the correct way to enable static website hosting on an S3 bucket?

easy

A. Enable 'Static website hosting' in bucket properties and specify index document

B. Set bucket policy to private and upload files

C. Create an IAM user with full access to the bucket

D. Attach an EC2 instance to the bucket

Solution

1. Step 1: Locate the static website hosting setting

   In the S3 bucket properties, there is an option to enable static website hosting where you specify the index document.

2. Step 2: Understand the correct configuration

   Enabling static website hosting and setting the index document allows the bucket to serve web pages correctly.

3. Final Answer:

   Enable 'Static website hosting' in bucket properties and specify index document -> Option A

4. Quick Check:

   Enable hosting + index document = correct setup [OK]

Hint: Enable hosting in properties and set index file name [OK]

Common Mistakes:

• Leaving bucket policy private without public read
• Confusing IAM user creation with hosting setup
• Trying to attach EC2 to S3 bucket

3. Given this bucket policy snippet for an S3 static website:

{
  "Version": "2012-10-17",
  "Statement": [{
    "Effect": "Allow",
    "Principal": "*",
    "Action": "s3:GetObject",
    "Resource": "arn:aws:s3:::example-bucket/*"
  }]
}

What is the effect of this policy?

medium

A. Allows only authenticated users to write to the bucket

B. Blocks all access to the bucket

C. Allows anyone to read objects in the bucket

D. Allows anyone to delete objects in the bucket

Solution

1. Step 1: Analyze the policy statements

   The policy allows "Effect": "Allow" for "Principal": "*" which means everyone, on the action "s3:GetObject" for all objects in the bucket.

2. Step 2: Understand the permission granted

   This means anyone can read (get) objects from the bucket, which is needed for public website hosting.

3. Final Answer:

   Allows anyone to read objects in the bucket -> Option C

4. Quick Check:

   Principal * + GetObject = public read [OK]

Hint: Principal * with GetObject means public read access [OK]

Common Mistakes:

• Thinking it blocks access instead of allowing
• Confusing GetObject with write or delete permissions
• Assuming only authenticated users have access

4. You enabled static website hosting on your S3 bucket but get a 403 Forbidden error when accessing the site. What is the most likely cause?

medium

A. Index document is missing from the bucket

B. Bucket policy does not allow public read access

C. Bucket name contains uppercase letters

D. You did not upload any files

Solution

1. Step 1: Understand 403 Forbidden error context

   A 403 error usually means permission denied, so the website cannot read files from the bucket.

2. Step 2: Check bucket policy and permissions

   If the bucket policy does not allow public read access, the website cannot serve files, causing 403 errors.

3. Final Answer:

   Bucket policy does not allow public read access -> Option B

4. Quick Check:

   403 error = permission denied = fix bucket policy [OK]

Hint: 403 means permission denied; check bucket policy [OK]

Common Mistakes:

• Assuming missing index document causes 403 (usually 404)
• Thinking bucket name case causes errors
• Ignoring permissions and blaming missing files

5. You want to host a static website on S3 with a custom domain and HTTPS. Which combination of AWS services should you use?

hard

A. S3 static website hosting + Route 53 for domain + CloudFront with SSL certificate

B. S3 static website hosting + EC2 instance + Elastic Load Balancer

C. S3 static website hosting + Lambda functions + API Gateway

D. S3 static website hosting + DynamoDB + IAM roles

Solution

1. Step 1: Identify services for custom domain and HTTPS

   Route 53 manages domain names, CloudFront provides HTTPS with SSL certificates, and S3 hosts the static files.

2. Step 2: Understand the integration

   Use Route 53 to point your domain to CloudFront distribution, which serves content securely from S3 with HTTPS.

3. Final Answer:

   S3 static website hosting + Route 53 for domain + CloudFront with SSL certificate -> Option A

4. Quick Check:

   Custom domain + HTTPS = Route 53 + CloudFront + S3 [OK]

Hint: Use CloudFront for HTTPS and Route 53 for domain [OK]

Common Mistakes:

• Using EC2 or Lambda unnecessarily for static hosting
• Ignoring CloudFront for HTTPS support
• Confusing database or IAM roles with hosting setup