AWS Custom Domain Redirect with S3 and Route 53

Andrew Alba — Fri, 18 Feb 2022 02:36:47 +0000

Working with a client who has been using Zoom video conferencing frequently, I suggested a pretty URL to help clients access the Zoom meetings.

I decided that I wanted to create a URL that was something like https://zoom.custom-domain.com/ that would redirect to Zoom meeting link such as https://us02web.zoom.us/j/94220614975?pwd=et9bd32Av2JC2yCtQifmA8ZoRpfxB6Nr. In the past, I would construct the redirect using .htaccess or through the domain name registrar console.

The client had a static site using a custom domain that was hosted on AWS using S3, CloudFront, and Route 53. I initially thought I could do this with the hosted zone for the client's domain name. I soon learned AWS has a different process for this type of redirect. Log into your AWS console and follow along.

S3 Bucket Redirect

To create the redirect, we need to start by creating an S3 Bucket. It didn't make much sense to me at first, but we will connect the dots later.

Navigate to the S3 service in your console.
We used the domain URL to name our bucket zoom.custom-domain.com. Be sure to uncheck the Block all public access under Block Public Access settings for this bucket section. You will need to check the box that appears to acknowledge this change.
Click the Create bucket button.
Click the bucket name in the list of buckets to open the bucket.
Select the Properties tab.
Scroll to the bottom of the page and click the Edit button within the Static website hosting section.
Select the Enable radio button under Static website hosting.
Select the Redirect requests for an object radio button under Hosting type.
Enter the redirect URL within the Host name field.
Select your Protocol.
Click the Save changes button to complete.

Our redirect is now in place and you can test by scrolling back down to the Static website hosting section and using the redirect link.

Add Redirect to Route 53

Navigate your browser to Route 53 service and click on the Hosted zones link to list the hosted zones.
Select/click the hosted zone we would like to add a record too.
Under the Records section click the Create record button.
Toggle the Alias on.
Enter your subdomain value in the record name field. In our example it is zoom.
Under the Route traffic to option, select Alias to S3 website endpoint. Select your region and then select the S3 bucket redirect created above.
Click the Create records button.

Once the host record propagates, the URL should redirect. Test it out in your browser.

Conclusion

This wasn't the solution I expected when I started on this path, but the implementation is simple. Hopefully, you found these instructions useful. If you have any comments, feel free to share them.

Best of luck and cheers!

Deploying a Secure Static Site to AWS with S3, Route 53 and CloudFront

Andrew Alba — Sat, 12 Feb 2022 22:26:00 +0000

There probably hasn't been a better time to host static websites than today. As a developer, you can use some excellent free services such as Netlify, Github, and Firebase.

Hosting a static site in the cloud with companies such as AWS, Heroku, and DigitalOcean can be done at a low cost as well.

Being most familiar with AWS, this is the route I have chosen for a client. These instructions will likely be outdated within a year but should offer some guidance for anyone trying to create a static site that takes advantage of the features and services provided by AWS.

AWS

There are several economic reasons for using AWS to host a static site. AWS provides developers with a free tier for many of their services. Bandwidth and storage costs are low because of the large scale of AWS. AWS can help us manage our custom domain with certificate management, hosted zones, and a content delivery network.

My intention is to provide guidance through this process of setting up and hosting an HTTPS-enabled static website using AWS services with a custom domain. I use Namecheap for domain name registrations, but these instructions can be applied with other registrar services.

There are a few assumptions that will be made for this guide.

You have an AWS account or can create an account before starting the guide.
You have a custom domain registered and access to modify nameserver.
You have about thirty minutes to complete this guide.

Here are the four services we will be using with our static website project.

AWS Certificate Manager or ACM. We can generate an SSL certificate for our custom domain name with this service and set up HTTPS for our site.
Simple Storage Service or S3. As the name suggests, we can upload our static content to a bucket, and serve the files to website visitors.
CloudFront. This is the AWS content delivery network. The service distributes static content to nodes around the globe. This service improves the user experience for worldwide traffic. CloudFront will add a small cost to our hosting fees but provide free SSL termination for HTTPS.
Route 53 is the service to manage our DNS records. This service integrates our custom domain from NameCheap to our CloudFront distribution.

Route Traffic From Our Custom Domain to Route53

Log into your AWS account and open the Route 53 dashboard. In the left navigation, select the Hosted Zone link. Once the Hosted Zone page loads, find and click the Create hosted zone button.
Add your Domain name and a description of the hosted zone record. Leave the default type Public hosted zone selected. Add any tags you would like and click the Create hosted zone button.
Once your hosted zone is created, select the hosted zone and click the View details button.
Expand the Hosted zone details and take note of the name server records. We will need to use these for our custom domain.
Open a new browser tab and use that to log into your custom domain registrar. Navigate to manage the domain nameservers. For Namecheap navigate to a list of our domains and then click the Manage button. Scroll down to the name server section and change the selected name server from Namecheap BasicDNS to Custom DNS. Under the selection, you can now enter the name server records from step 4. Depending on the registrar, the propagation time of these changes can vary. In my experience, the propagation only takes a few minutes, but it can be several hours for some.

Generating an SSL certificate

Open a new browser tab and navigate to the ACM service. Click on the Request a certificate button. If viewing the certificate list, click on the Request button.
Under Certificate Type, verify the default Request a public certificate is selected and click the Next button.
Add all fully qualified names you plan to use in the Domain section. Keep the default selected DNS validation under the Select validation method. Add any tags (optional) and then click the Request button.

Generation of the certificates will take some time. Once the certificate generates, click on the Certificate ID link to view the certificate. Scroll to the Domains section and take note of the CNAME records. These records will need to be added to the Route 53 hosted zone.

Connect Certificates to Hosted Zone

Open the Route 53 hosted zone tab and click on the domain name link to access the records. Scroll down to the Records section and click on the Create record button.
If there is a subdomain record, add that prefix to the Record name. If this is the root domain, leave the field empty. Change Record Type to CNAME. Paste the CNAME value from the certificate record into the Value field.
If you have more than one record, click the Add another record button and repeat the step 2 instructions for each record. Once completed, click the Create records button.

Note: We will need to confirm that the certificate has been associated with the hosted records later.

Create an S3 bucket for Static Hosting

Navigate to AWS S3 and click on the Create bucket button.
S3 buckets are global, so you will need to use a unique bucket name. Use your domain name as your Bucket Name. Scroll down and uncheck the Block all public access box under the Block Public Access settings for this bucket section. Scroll to the bottom and select the Create bucket button.
After the bucket has been created, navigate to the Permissions tab of the bucket and scroll down to the Bucket policy section. Click the Edit button and create a bucket policy to allow public read access to the bucket.

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

Within the bucket select the Properties tab. Scroll down to the Static web hosting section (at the bottom of the page) and click the Edit button.
Select Enable under Static website hosting and Host a static website under Hosting type. Add the static sites Index document (index.html for most) and then click the Save changes button.
After saving, we should have a URL for the static website provided by S3 (example: http://example.com.s3-website-us-east-1.amazonaws.com). Take note or copy this URL as we will need this to create our CloudFront distribution.
Upload all of your static website files to the S3 bucket. You should be able to verify your site using the link provided in step 5.

Create CloudFront Distribution

Before we start this process, we will want to make sure our SSL certificate has been successfully connected to the hosted zone. Navigate back to the ACM and wait/refresh until the Status shows success.

Go to the CloudFront dashboard and click the Create Distribution button.
In the Origin domain field paste in the S3 static website URL from step 5 of creating an S3 bucket. The Name section should populate with the bucket name (example: example.s3-website-us-east-1.amazonaws.com).
Scroll down to Default cache behavior section and select Redirect HTTP to HTTPS under Viewer protocol policy.
Scroll to Settings and be sure to select the price class that is best for your website. If your static hosted site is intended for use in the US only, select Use only North America and Europe for example.
Click the Add item button under the Alternate domain name (CNAME) heading and add each one of your domains.
Within the selector for Custom SSL certificate, choose the SSL certificate for our custom domain.
Scroll to the bottom and click the Create distribution button.

The CloudFront distribution will take several minutes to generate. Once the distribution is completed, you should be able to access your website using the secure custom domain.

After making updates to your site and uploading the changes to your S3 bucket, you will want to look at creating an invalidation with the CloudFront distribution.

Some Pro Tips for AWS

Within your AWS account, make sure you view your billing dashboard. Within the billing dashboard, you can create a budget. Be sure to use this and create a budget that is acceptable for your use. This can save you from spending more money than you expect in a monthly billing period.

Within CloudWatch, set up a billing alarm for your AWS spending. This can alert you of any unexpected services that you may have left running.

Take advantage of AWS SDK written in your preferred development language for automating deployments and creating invalidations for your CloudFront distributions.

Conclusion

While the tutorial was not as detailed as I initially intended, it is my hope that the tutorial is enough to make your static website public to users. Please take some time to implement the pro tips above and spend some time learning more about the four AWS services we have discussed.

If you have found this tutorial useful and would like to connect, follow me on twitter.

Best of luck and cheers!

Cover image by Caspar Camille Rubin

DEV Community: Andrew Alba

AWS Custom Domain Redirect with S3 and Route 53

S3 Bucket Redirect

Add Redirect to Route 53

Conclusion

Deploying a Secure Static Site to AWS with S3, Route 53 and CloudFront

AWS

Route Traffic From Our Custom Domain to Route53

Generating an SSL certificate

Connect Certificates to Hosted Zone

Create an S3 bucket for Static Hosting

Create CloudFront Distribution

Some Pro Tips for AWS

Conclusion