How to enable HTTPS with Naked Domain and Protocol Redirects on your S3 Website (Part Two)

Part Two of this HOWTO demonstrates how to secure your S3 hosted website with HTTPS. If you haven't completed part one yet, be sure to click here.

Once you complete this HOWTO, you will have a secure website, that Google approves, as seen in the screengrab below:

Qualys Results

HTTPS and Naked Domain redirection will increase your security, reduce customer bounce rate and increase SEO.

Outline

In part one of this tutorial, we will executed the following:

  1. Configure DNS (Route 53)
  2. Create Log, WWW and Naked Domain S3 Buckets
  3. Configure S3 Bucket Naked Domain and Protocol Redirection
  4. Request a Certificate

In part two of this tutorial (this post), we will:

  1. Upload a web page
  2. Create CloudFront distribution
  3. Point DNS (Route 53) to CloudFront distribution

As a reminder, to show the process in action, I demonstrate how to set up HTTPS with Redirection on S3 using a real world site, www.siliconebeltway.com. In this demonstration, you would simply replace siliconebeltway with your website's domain name.

As described in part one, the following diagram depicts our desired Architecture:

Route 53 Cloudfront S3

Upload a web page

I will use a simple hello world web page to make sure everything works. At this point, you could upload an existing static website. In this example, I assume your site uses index.html for the main page's name.

First, go to the S3 console:

Find Route 53 Console

Then, select the bucket that will serve the web pages, the bucket that starts with www. I select www.siliconebeltway.com:

Select S3 Bucket

On the "Overview" tab, selct "+ Upload:"

Select Web Page

Click the "Add Files" box. I created a document on my Desktop named index.html. I entered the text "Coming Soon!" into the file and saved it. I will upload this index.html file to test the website (once we're finished configuring it).

Select Add Files

Click next. Again, for purposes of this demo, ensure that you named the main page index.html.

Select Next

Again, on the 'Upload' screen, ensure that you grant public access.

Grant Public Access

Now that you have a test file uploaded, see if AWS completed your certificate validation.

Create CloudFront distribution

S3 does not natively support HTTPS for websites, so we will use CloudFront. We requested a certificate from ACM to install into CloudFront. Check to see if ACM completed issuing the certificate. It takes about a half of an hour to complete. Go to the Certificate Manager console, click your website, and wait until you see the following success page. Ensure that both the naked and www domain completed.

Certificate Validation Complete

If it completed, open the CloudFront console from the main AWS console.

Open Cloudfront Console

Select "Create Distribution."

Select Create Distribution

Select "Get Started" under "Web Delivery."

Select HTTP Delivery

We will first create the www CloudFront distribution. If you look at the architecture diagram at the start at this blog post, you see we enable protocol (HTTP to HTTPS) redirection for the www bucket at the CloudFront distribution. Under "Origin Domain Name," select your www bucket. I select www.siliconebeltway.com.s3.amazonaws.com. The console will auto-populate the "Orgin-ID" bucket with S3-www.siliconebeltway.com. If not, select it there. In this section, be sure to enable HTTP to HTTPS redirection by selecting that radio button. I highlight the appropriate fields in green below.

Configure WWW Distribution And Protocol Redirection

In order to point Route 53 to your cloudfront distribution, you must enter a CNAME under 'Distribution Settings.' Enter www.siliconebeltway.com. You also must select the ACM generated SSL/TLS certificate for your website. Click 'Custom SSL Certificate' and then select the certificate for your domain.

Set CNAME and TLS Certificate

Now enable logging. Turn on logs and select the log bucket you created. These logs will show you who visited your site and their location. I show you one method to view S3 logs in this blog post.

Enable Logging

Once you click through all the confirmation menues, you will get back to the CloudFront console. You will see the progress of the www CloudFront distribution deployment. Now, create a distribution for the naked domain. Click "Create Domain."

View Progress And Create Naked Domain Distribution

Again, select the naked S3 bucket under 'Origin Domain Name.' I select siliconebeltway.com.s3.amazonaws.com. CloudFront will pre-populate "Origin-ID" with S3-siliconebeltway.com (if it does not, select it). Under 'Default Cache Behavior Setting --> Viewer Protocol Policy' select 'HTTP and HTTPS.' If you look at the Architecture diagram at the beginning of this post, you will see we execute HTTP to HTTPS protocol redirection at the naked S3 bucket. For that reason, we do not need to redirect here, since that would result in an unecessary redirection.

Select Bucket And Allow HTTP And HTTPS

Once more, set the CNAME (i.e. siliconebeltway.com) and select the SSL/TLS certificate for your naked domain name.

Set CNAME And TLS Certificate

Now enable logging, and point to your log bucket.

Enable Logging

Click through all the 'Save' menus and you will be taken back to the main CloudFront console. Wait until the deployment completes. Once it does, you will see the following success screen.

Deployment Complete

Point DNS (Route 53) to CloudFront distribution

From the main AWS console, open Route 53.

Find Route 53 Console

Click on your hosted zone and then click "Create Record Set."

For "Name" enter www. Select "A - IPv4" address under Type. Select "Yes" for Alias, and then select your www CloudFront distribution. I select www.siliconebeltway.com.

Point DNS To WWW Distribution

Route 53 may bark. If you waited for the distribution deployment to complete, then you can ignore the warning and click save.

Review Alias

Be sure to repeat the process and create a record for your naked domain (just leave the 'Name' field blank) and be sure to point the Alias to your naked CloudFront distribution.

Once Route 53 finishes the updates (five minutes or so), you can go to your website. If you go to any combination of naked or www domain with or without HTTPS the system will redirect to the www domain with HTTPS.

If you click the secure icon (which goes away in July 2018), you will see that Google trusts the site!

Success

Please leave a comment below, and check out some of my other AWS tips and tricks. You may also want to view the access logs of your website.

Show Comments