Simple HTTP Redirects Using AWS Route 53 and S3


Let’s just say that you want to create a redirect for a root domain while using Route 53 on Amazon Web Services.  Many of the popular domain registration and web hosting providers (e.g. GoDaddy,, etc.) have baked in settings to redirect to another URL.

In Route 53, there is no native way to do this, but luckily it’s a couple of simple steps away and you also get to learn a little about web site hosting on AWS S3 (Simple Storage Service) at the same time.

My example is for which has been redirected to as you can see by clicking the link.  Now, let’s learn how to do that easily with AWS Route 53 DNS service and S3.

Our assumption is that you’ve registered the domain with Route 53 or are at least hosting the DNS zone and have set the SOA (Start of Authority) record and NS (Name Server) records to AWS DNS settings.

Setting up Your S3 Buckets

The reason that I say buckets as a plural, is that we will want to have a working DNS for both the root domain and also the which is normally a CNAME entry to point to the root domain.

Open up your AWS S3 and click the Create Bucket button.  Name your S3 bucket the same as your domain name.  In my case for the example is  I’ve chose to put it in the US Standard region because it’s the closest to the majority of my traffic for the site:



After you click the create button, you need to click the Properties button on the upper right side of the page.  Expand the section which says Static Website Hosting, select the Redirect all requests to another host name radio button, and type the URL that you want to redirect to.  In my case it is


Save the changes and repeat the process, but this time you will name the S3 bucket as the www name for your domain.  My example uses


Open the Properties section, expand the section which says Static Website Hosting, select the Redirect all requests to another host name radio button, and type the URL that you want to redirect to:


That is your S3 configuration.  Next up is the DNS settings.

Route 53 Configuration for S3 Targets

Open up your Route 53 configuration in the AWS console.  Select the Hosted Zones area, choose the radio button for the zone we are working on and click Go to Record Sets:


Click Create Record Set.  Leave the Name section empty, choose A – IPv4 address as the Type:


Change the Alias from the default of No to Yes:


Click in the Alias Target field which brings up a droplist.  It may take up to 20 or more seconds to populate the list.  Under the S3 website endpoints you will see the one you’ve created.  Select that and click the Create button at the bottom:


Repeat the process of adding a new record.  This time put www in the Name section.  Keep A-IPv4 address as the Type, and click the Alias Target section to select the S3 website endpoint which matches the A record name:


DNS is a rather magical system, but it will take up to 15 minutes or more update.  Once some time has passed, you can confirm te redirection is in place by trying the URL in a browser.  It should redirect you to the web site that you’ve assigned in your S3 configuration.

You can confirm from the command line using cURL as well.  Type curl --head which will show you the output below, and then you can also type curl which will show you the redirect in the output:


Note that this is different than a 301 or 302 redirect.  The method used by the S3 redirection is a META tag instead.  I’m also assuming that you’re aware that there is a cost for the S3 usage.

Costs of Using S3 for Web Site Hosting and Redirection

As listed on the S3 and storage pricing site, the S3 usage qualifies for a Free Tier to AWS users up to the first 20,000 HTTP GET requests per month for the first year of usage.


After your Free Tier usage expires, you are charged 0.004$ per 10,000 HTTP GET requests per month in the US East region.  Pricing across regions can be different, so make sure to take that into account when you choose the location of your S3 buckets:


Hopefully this helps, plus it’s also handy to know as part of your study towards the AWS Solutions Architect Associate exam.


People, Process, and Technology. Powered by Community!

You might also like


  • Varun
    August 22, 2016 at 5:27 am

    Instead of creating a second bucket for redirecting, can’t we create a CNAME record for that points to How is it better to create two buckets instead of adding the CNAME record.

    • DiscoPosse
      September 7, 2016 at 3:19 pm

      Hi Varun,

      You can also achieve the same result using the CNAME and pointing to the FQDN URL of the S3 target for the root bucket. I prefer the dynamic mapping because it also makes sure that during a failover or any change behind the scenes that it is done automatically as a clean redirect.

      Hopefully that answers it for you.



      • DiscoPosse
        September 7, 2016 at 3:20 pm

        the shorter answer would be…yes 🙂


Proudly Sponsored By

infinio nutanix vembu Turbonomic

GC On-Demand

Subscribe to the Blog

Enter your email address to subscribe to this blog and receive notifications of new posts by email.

Upcoming events:

no event