How To Host S3 Static Website With Custom Route 53 Domain (4 Min) | AWS | Set Alias To S3 Endpoint

Gokce DB

31 Mar 202304:10

Summary

TLDRIn this tutorial, ABI from gokjdb demonstrates how to host a static website using Amazon S3 and Route 53 with a custom domain. The video guides viewers through creating an S3 bucket with the same name as the domain, uploading an index.html file, configuring the bucket for static website hosting, and making the objects public. It also covers setting up a Route 53 record with the custom domain to point to the S3 bucket, ensuring the website is accessible via the custom domain. The video concludes with a reminder to check for the DNS change to sync and a prompt for likes, subscriptions, and notifications.

Takeaways

🌐 Start by navigating to the S3 service in AWS to create a new bucket with a name that matches your custom domain.
📝 Leave the region as US East 1 and enable ACLs, but uncheck 'Block all public access' to make objects public.
🚫 Acknowledge the warning about making all objects in the bucket public.
📂 After creating the bucket, upload the index.html file which contains the website's content, such as a 'Hello World' message.
⚙️ Go to the bucket's properties, enable static website hosting, and specify 'index.html' as the index document.
🔄 If you encounter a '403 Forbidden' error, make the index.html file public using the ACLs.
🌐 Visit the Route 53 service to manage your custom domain and create a new record.
📝 Use the same name for the record as your S3 bucket and select 'Simple Routing' for the record type.
🔄 Choose 'Alias' for the record type and link it to the S3 website endpoint you created earlier.
📍 Select the correct region for the S3 endpoint and ensure the record is linked to it.
👀 Wait for the DNS changes to sync and then check your custom domain in a new browser to confirm it's routing to the S3 endpoint.

Q & A

What is the main topic of the video?
-The video is about teaching viewers how to host a static website using Amazon S3 with a custom Route 53 domain in AWS.
What is the first step in creating a static website on S3?
-The first step is to navigate to the S3 service and click on 'create bucket', giving it a name that matches your custom domain.
Why is it important to choose the correct region for the S3 bucket?
-Choosing the correct region ensures that your website's data is stored and served from a location that is geographically close to your audience, which can improve load times.
What does enabling ACLs mean in the context of the S3 bucket?
-Enabling ACLs (Access Control Lists) allows you to control who has access to the bucket and its contents.
Why should you uncheck 'Block all public access' when creating the S3 bucket?
-Unchecking 'Block all public access' is necessary because the video tutorial requires the bucket's objects to be public for the website to be accessible.
What file is uploaded to the S3 bucket to serve as the website's homepage?
-An 'index.html' file is uploaded, which contains the content to be displayed on the homepage of the website.
How do you enable static website hosting for the S3 bucket?
-You navigate to the 'properties' tab of the bucket, scroll down to the 'static website hosting' section, click 'edit', enable static website hosting, and specify the index document name.
What is the purpose of the 'make public using ACL' action on the S3 objects?
-The 'make public using ACL' action is used to grant public access to the objects in the bucket, which is required to resolve the 403 Forbidden error and make the website accessible.
What is the process for creating a record in Route 53 to link the custom domain to the S3 bucket?
-You navigate to the 'hosted zones' in Route 53, select your hosted zone, click 'create record', choose 'simple routing', define the record with the same name as the S3 bucket, set the record type to 'A' or 'Alias', and choose the S3 website endpoint as the Alias target.
Why is it necessary to wait for the Route 53 changes to be 'in sync'?
-Waiting for the changes to be 'in sync' ensures that the DNS propagation is complete and the custom domain is correctly pointing to the S3 bucket before testing the website.
How can you confirm that the custom domain is correctly routing to the S3 endpoint?
-You can confirm this by opening a new browser session and visiting your custom domain to see if it displays the content of the S3 bucket's static website.

Outlines

00:00

🌐 Hosting a Static Website on S3 with Custom Domain

ABI from gokjdb introduces viewers to the process of hosting a static website using Amazon Web Services (AWS). The tutorial begins with creating an S3 bucket with a name that matches the custom domain. The bucket is set up in the US East 1 region with ACLs enabled but public access blocked. The video demonstrates uploading an 'index.html' file, which contains a simple 'Hello World' message in H1 tags. The properties of the bucket are then configured for static website hosting, with the index document specified. The tutorial also covers resolving a 403 Forbidden error by making the objects public through ACLs and verifying the website's accessibility.

🔄 Configuring Route 53 for Custom Domain Routing

Continuing the tutorial, the video script explains how to set up a custom domain with Amazon Route 53. This involves navigating to the hosted zones and creating a record that matches the S3 bucket name. The record type is set to A or Alias, and the endpoint is configured as an Alias to the S3 website endpoint. The region is selected as US East 1, and the S3 endpoint is automatically populated. After creating the record, the status is monitored until it changes from 'Pending' to 'In Sync'. The final step is to confirm in a new browser session that the custom domain is correctly routing to the S3 endpoint, completing the setup process.

Mindmap

Keywords

💡S3

S3 stands for Simple Storage Service, which is a service provided by Amazon Web Services (AWS) for storing and retrieving any amount of data, at any time, from anywhere on the web. In the video, S3 is used to host a static website, which is a website that does not require server-side processing and can be served directly from the S3 bucket.

💡Custom Domain

A custom domain refers to a domain name that is unique to the owner and is used to identify a website on the internet. In the script, the custom domain is 'testing.gokjdb.com', which is used to access the static website hosted on S3.

💡Route 53

Route 53 is a highly available and scalable Domain Name System (DNS) web service provided by AWS. It is used to route users to the website by translating human-friendly domain names, such as 'testing.gokjdb.com', into IP addresses that computers use to connect to each other on the internet.

💡Bucket

In the context of AWS S3, a bucket is a basic container that holds your data. The video script describes creating a bucket with a specific name that matches the custom domain, which is essential for hosting the static website.

💡ACLs (Access Control Lists)

Access Control Lists (ACLs) are used to define permissions for Amazon S3 buckets and objects. In the script, ACLs are enabled but with a note of caution to uncheck 'block all public access', which is important for the bucket to be accessible over the internet.

💡Static Website Hosting

Static website hosting refers to the service provided by AWS S3 to host websites that consist of static HTML, CSS, and JavaScript files. The script explains how to enable this feature for an S3 bucket to serve the website's content.

💡Index Document

An index document is the main page that is served when a visitor accesses the root URL of a website. In the video, 'index.html' is specified as the index document for the static website hosted on S3.

💡Public Access

Public access refers to the ability of anyone on the internet to view or download the content stored in an S3 bucket. The script mentions making the objects in the bucket public to resolve a '403 Forbidden' error, allowing the website to be accessible.

💡Record

In the context of Route 53, a record is a mapping between a domain name and an IP address. The script describes creating a record in Route 53 to point the custom domain to the S3 bucket's website endpoint.

💡Alias

An alias in Route 53 is a type of record that points a domain to another resource, such as an S3 bucket, without changing the domain's IP address. The script uses an alias record to direct the custom domain to the S3 bucket's website endpoint.

💡DNS Propagation

DNS propagation refers to the time it takes for changes made to the DNS records to take effect worldwide. The script mentions waiting for the DNS changes to go from 'pending' to 'in sync', which is necessary for the custom domain to correctly route to the S3 bucket.

Highlights

Introduction to hosting a static website using S3 with a custom Route 53 domain in AWS.

Navigating to the S3 service and creating a new bucket with a name matching the custom domain.

Choosing the correct region and enabling ACLs while configuring the bucket.

Disabling 'Block all public access' and acknowledging the warning about making objects public.

Uploading the index.html file to the S3 bucket for the website.

Setting up the properties for static website hosting and specifying the index document.

Accessing the bucket website endpoint to check the website's initial accessibility.

Troubleshooting the 403 Forbidden error by making the objects public using ACL.

Refreshing the website endpoint to display the 'hello world' message after making objects public.

Moving to Route 53 service to configure the custom domain.

Creating a record in the hosted zone with the same name as the S3 bucket.

Selecting the correct record type and endpoint for the S3 website.

Choosing the appropriate region for the S3 endpoint.

Automatic population of the S3 endpoint in Route 53 and creating the record.

Checking the status of the DNS changes and waiting for them to sync.

Confirming the custom domain routing to the correct S3 endpoint in a new browser session.

Encouraging viewers to like, subscribe, and turn on notifications for future content.