How to configure Cloudflare for AWS Route53

In this post you will learn about How to configure Cloudflare for AWS Route53 hosted name via Cloudflare as a proxy.

Resources Used:

What is Cloudflare : Cloudflare provides content delivery network services, DDoS mitigation, Internet security  and distributed domain name server services.Cloudflare’s services sit between the visitor and the Cloudflare user’s hosting provider, acting as a reverse proxy for websites. Please check About Site to see how cloudflare used as a proxy for They have different pricing models ranging from Free service with limited features to pay per service for all other available features.

AWS Route53: Amazon Route 53 is a highly available and scalable Domain Name System (DNS) web service. It is designed to give developers and businesses an extremely reliable and cost-effective way to route end users to Internet applications by translating human readable names.

Route 53 performs three main functions:

  • Domain registration.
  • DNS service.
  • Health check.

In addition you can check for key AWS Services here.

Before registering on Cloudflare, we should have our own website, DNS registered let’s say with and AWS Route53 as a hosted zone. How to register  hosted zones using AWS Route53 was already discussed in our blog: ‘Route53 -WebSite hosting Example‘ , in case if you have not already registered a hosted zone, please register with the same.

For free host name registration instead of you can try others like  ‘‘ , ”‘ , ‘‘ and a lot out there as well.

How to Configure Cloudflare for AWS Route53

1) Sign-up using your email id:

2) Add your your website host name.

CloudFlare registration

3) Select a (free website) plan for your website and click continue.

free plan

4) Once the plan is selected, the next page will automatically retrieve the NS records from Route53 and provide an equivalent Cloudflare NS record.

NS Record

5) Copy the cloudflare equivalent NS records and click continue, which will take you to next page(status pending till the change is complete at DNS provider side or where you bought your host name). cloudflare status pending

6) Simultaneously go to your host name provider (godaddy) to edit the NS records . Manage DNS / change the custom DNS to the newly generated NS records as copied above. You can edit the existing records and replace with these or delete the existing NS records and add these Cloudflare equivalent NS records and save.

7) Once the NS records are update and saved in DNS provider side, it may take couple minutes for the cloudflare status to change to Active, even though description says ‘Allow upto 24 hours …‘ . Once status is changed, you will find your website name status as Active.

cloudFlare Active

8) That’s all required, to make your site registered at cloudflare. Now on cloudflare will act as  proxy between User & Route53 hosted zones and serve the visitor. You can refresh your website to start Cloudflare to serve the content.

9) Now you can enable a free feature SSL encryption for your website, make sure SSL certificate is active before updating your site address to https to give your users a secure access.SSL activation may take some time or even hours. Wait till you see Crypto – > SSL Certificate Active. You can change your site url to start with or redirect to https instead of http.

Cloudflare SSL

You may also like...