AWS Builder Center

From Free Domain to Live HTTPS Website: Route 53, ACM, S3 and CloudFront

A two-part, hands-on walkthrough for delegating a free domain to AWS and hosting a secure static website behind CloudFront — no domain purchase required.

Software Development Engineer

Video Demo

In case you get stuck between any step you can reference the video.


Why this project

One of the biggest blockers for beginners who want to practice real AWS networking and hosting skills is cost: a custom domain usually means paying a registrar. This project removes that blocker entirely. You'll claim a free domain from DNSExit, delegate it to Route 53, issue a free public SSL certificate with ACM, and serve a static website from S3 through CloudFront — all reachable over  https://yourdomain.com  with a valid padlock in the browser.
By the end of these two labs, you'll have hands-on reps with the exact pattern real production static sites use: DNS delegation → certificate validation → private S3 origin → CDN distribution → alias record.
Watch the full walkthrough in the video demo attached to this post, and follow along below.



Architecture

  • A visitor types your domain in the browser.
  • Route 53 is authoritative for DNS and answers the query — it also holds the CAA and alias records that make the rest of this possible.
  • The domain registrar (DNSExit, free) only handles the initial registration; nameserver authority is delegated to Route 53 in Lab One.
  • ACM issues and manages a free TLS certificate, validated entirely through DNS records in Route 53.
  • CloudFront sits in front of the origin, terminates HTTPS using the ACM certificate, and caches content at edge locations worldwide.
  • S3 stores the actual website files and stays fully private — CloudFront reaches it through Origin Access Control (OAC), never over the open internet.



Lab One: Delegate a free DNSExit domain to Route 53 and issue an ACM certificate

Goal: Get a real domain name pointing at AWS-managed DNS, then prove to ACM that you own it so it will issue you a free, publicly trusted SSL certificate.
Architecture

Prerequisites
  • An active AWS account
  • A free DNSExit account
  • A terminal with  dig  installed (Linux/macOS, or Git Bash/WSL on Windows)

Part 1 — Claim a free domain on DNSExit

  1. Log in at DNSExit.com and go to Free Domains / Hostnames (or DNS Services → Free DNS).
  1. Pick an available extension — for example  .run.place ,  .work.gd , or  .linkpc.net .
  1. Enter a custom prefix (e.g.  yourdomain ) to build your full domain, like  yourdomain.run.place .
  1. Complete the registration form.

Part 2 — Create a hosted zone in Route 53

  1. Open Route 53 in the AWS Management Console.
  1. Go to Hosted zones → Create hosted zone.
  1. Enter the exact domain string from DNSExit, and set the type to Public hosted zone.
  1. Click Create hosted zone.
  1. Open the new hosted zone and find the NS record — it contains four AWS nameservers, e.g.:
ns-1872.awsdns-42.co.uk.
ns-680.awsdns-21.net.
ns-1235.awsdns-26.org.
ns-2.awsdns-00.com.

Copy all four — you'll need them in the next step.

Part 3 — Delegate authority from DNSExit to Route 53

  1. Back in the DNSExit dashboard, go to Domain Management → Edit/Update Domain.
  1. Open Name Servers (or Custom Name Servers).
  1. Remove the default DNSExit nameservers and paste in the four AWS Route 53 nameservers.
  1. Save.
This is the step that hands DNS authority for your domain over to AWS — from here on, every record you need (CAA, certificate validation, website alias) is created inside Route 53.

Part 4 — Verify delegation from the terminal (Can take 24hrs to update nameservers)

Confirm the internet actually sees Route 53 as authoritative before moving on:
dig NS yourdomain.run.place

Check the  ANSWER SECTION  — it should list your four  awsdns  nameservers instead of DNSExit's. For a cleaner check:
dig NS yourdomain.run.place +short

Once  awsdns  addresses show up, delegation is complete.

Part 5 — Add the required CAA records

Free/public subdomains often trip up ACM validation unless you explicitly authorize AWS to issue certificates for the domain. In Route 53, open your hosted zone and Create record:
  • Record name: leave blank (applies to the root domain)
  • Record type:  CAA 
  • Value:
0 issue "amazon.com"
0 issue "amazontrust.com"
0 issue "awstrust.com"
0 issue "amazonaws.com"
0 issuewild "amazon.com"
0 issuewild "amazontrust.com"
0 issuewild "awstrust.com"
0 issuewild "amazonaws.com"

Click Create records.

Part 6 — Request and validate the ACM certificate

  1. Open AWS Certificate Manager (make sure you're in us-east-1 — CloudFront only accepts certificates from that region).
  1. Request a certificate → Request a public certificate → Next.
  1. Under domain names, enter  yourdomain.run.place  and optionally  *.yourdomain.run.place  for subdomains.
  1. Choose DNS validation and click Request.
  1. Open the pending certificate and click Create records in Route 53 under the Domains section, then Create records. ACM inserts the required  _x2hash...  CNAME validation record for you automatically.

Part 7 — Final verification

Give it 2–5 minutes to propagate, then check:
  • ACM console: status should flip from  Pending validation  to  Issued .
  • Terminal:
dig CAA yourdomain.run.place +short

Expected output:
0 issue "amazon.com"
0 issue "amazontrust.com"
0 issue "awstrust.com"
0 issue "amazonaws.com"
0 issuewild "amazon.com"
...

With delegation verified and a validated certificate in hand, you're ready for Lab Two.



Lab Two: Host a secure static website on S3 behind CloudFront

Goal: Serve a static site from a fully private S3 bucket, front it with CloudFront for HTTPS and caching, and point your domain at it with a Route 53 alias record.
Architecture

Prerequisites
  • Lab One completed: domain delegated to Route 53, ACM certificate issued in  us-east-1 
  • A static website folder with at least an  index.html 

Part 1 — Create a private S3 bucket and upload your site

  1. Open S3 → Create bucket.
  1. Give it a globally unique name (e.g.  bucketcreatedstep1 ).
  1. Keep Block all public access ENABLED — CloudFront will reach the bucket securely through Origin Access Control, so the bucket never needs to be public.
  1. Click Create bucket, then open it and Upload your website files, including  index.html .

Part 2 — Create a CloudFront distribution

  1. Open CloudFront → Create a CloudFront distribution.
  1. Distribution details: enter your custom domain name ( yourdomain.run.place ), keep the Route 53 zone selected so CloudFront recognizes your active zone, and choose Single website or app.
  1. Origin: set origin type to S3, select your bucket, and keep Allow private S3 bucket access to CloudFront (Recommended) — this configures Origin Access Control (OAC) for you.
  1. WAF: select Do not enable security protections to avoid extra cost during the lab.
  1. Certificate & root object: CloudFront auto-detects and attaches your ACM certificate from Lab One. Set Default root object to  index.html  (this prevents  AccessDenied  errors when someone visits the root URL). Review and click Create distribution.

Part 3 — Point your domain at CloudFront with an alias record

  1. Open Route 53 → Hosted zones and select your zone.
  1. Click Create record.
  1. Record name: leave blank (root domain). Record type:  A . Turn the Alias toggle ON.
  1. Route traffic to: choose Alias to CloudFront distribution, then select your distribution's domain ( dXXXXXXXXXXXXX.cloudfront.net ).
  1. Click Create records.

Part 4 — Verify and test

Wait 2–5 minutes for the CloudFront deployment and DNS propagation to settle.
Browser check: visit  https://yourdomain.run.place  — your site should load over HTTPS with a valid padlock.
Terminal check:
curl -I https://yourdomain.run.place

Expected response:
HTTP/2 200
content-type: text/html
server: CloudFront
x-cache: Hit from cloudfront
...

 x-cache: Hit from cloudfront  confirms CloudFront is serving from cache rather than hitting S3 on every request — exactly the behavior you want from a CDN.



Key takeaways

  • DNS delegation is the foundation. Once Route 53's nameservers are set at the registrar, every other record (CAA, certificate validation, website alias) lives in one place.
  • CAA records aren't optional for public/free domains — without them, ACM will silently refuse to issue a certificate.
  • Certificates for CloudFront must live in  us-east-1 , regardless of which region your other resources are in.
  • Keep S3 private. Origin Access Control lets CloudFront read from a fully locked-down bucket — there's no reason for the bucket itself to be public.
  • Alias records, not CNAMEs, for the root domain. Route 53's alias A record is what lets you point a bare domain (not just a subdomain) at a CloudFront distribution.

What's next

Try adding a second CloudFront behavior for API routes, set up S3 versioning so you can roll back deployments, or automate the whole pipeline with GitHub Actions so every push to  main  invalidates the CloudFront cache automatically.


Full step-by-step video demo above. Questions or stuck on a step? Drop a comment below.
Any opinions in this article are those of the individual author and may not reflect the opinions of AWS.
Enjoyed reading this content? Let the author know!

Your likes, comments, shares, and saves help creators reach more builders.

Loading recommendations

Loading article