Skip to main content

🌍 Amazon Route 53 Overview

Amazon Route 53 is a Managed DNS (Domain Name System) service.

  • DNS = "Phonebook of the Internet"
  • It helps clients resolve domain names (URLs) to IP addresses.
  • Route 53 supports multiple record types to map names to resources.

πŸ“˜ Common DNS Record Types​

Record TypeDescriptionExample
A RecordMaps domain β†’ IPv4 addresswww.example.com β†’ 12.34.56.78
AAAA RecordMaps domain β†’ IPv6 addresswww.example.com β†’ 2001:db8::7334
CNAME RecordMaps hostname β†’ another hostnamesearch.example.com β†’ www.example.com
Alias RecordMaps domain β†’ AWS resource (ELB, CloudFront, S3, RDS, etc.)example.com β†’ AWS Resource

🚦 How Route 53 Works (High-Level)​

  1. User enters myapp.mydomain.com in the browser.
  2. Browser sends a DNS query to Route 53.
  3. Route 53 returns the IP address for that domain.
  4. Browser connects to that IP β†’ reaches the correct server β†’ gets HTTP response.
IAM Roles Example

βš™οΈ Route 53 Routing Policies​

Used to determine how traffic is directed based on use case.

Routing PolicyHealth CheckDescriptionUse Case
Simple❌ NoReturns a single resource for a domainSingle web server
Weightedβœ… YesDistributes traffic across multiple resources based on assigned weightsLoad balancing (e.g., 70%-20%-10%)
Latency-Basedβœ… YesRoutes users to the region with the lowest network latencyGlobal apps β€” minimize latency
Failoverβœ… YesRoutes traffic to a standby resource when the primary failsDisaster recovery (active-passive setup)
IAM Roles Example

🧩 Key Exam Tips​

  • Route 53 = Managed DNS
  • Simple = 1 target, no health checks
  • Weighted = distribute load
  • Latency = choose nearest region
  • Failover = DR / backup routing
  • Alias records integrate with AWS resources (ELB, CloudFront, etc.)

🌐 Route 53 + EC2 β€” Latency-Based Routing​

This guide shows how to host simple web servers in two AWS regions and route users automatically to the lowest-latency region using Amazon Route 53.


1. Register a Domain (Route 53)​

  1. AWS Console β†’ Route 53 β†’ Create hosted zones
  2. Select Public hosted zone
  3. Click Create hosted zone
  4. This zone will store DNS records
IAM Roles Example
IAM Roles Example

2. Launch EC2 Instances (Two Regions)​

  • Security Group: allow HTTP (port 80) inbound
  • Launch, then copy each instance’s Public IPv4 Address
  • Ireland(54.155.150.72)
  • Oregon(34.214.42.89)

3. Create Latency-Based Records (Route 53)​

  1. Hosted Zone β†’ Create record
  2. Record name: www Type: A Routing policy: Latency
  3. Add first record:
    • Value: Ireland EC2 IP
    • Region: EU (Ireland) Identifier: β€œIreland-Instance”
  4. Add second record:
    • Value: US EC2 IP
    • Region: US West (Oregon) Identifier: β€œUS-Instance”
IAM Roles Example

4. Test Routing​

MethodCommand / Action
BrowserOpen http://www.himanshupapola.tech
DNSnslookup www.himanshupapola.tech
Cross-region testUse a VPN to switch regions and reload the site

Expected:

  • From Europe β†’ β€œHello from Ireland”
  • From US β†’ β€œHello from US”
IAM Roles Example

5. Cleanup​

TaskCommand / Action
Terminate EC2aws ec2 terminate-instances --instance-ids <IDs>
Delete DNS recordsRemove A records for www
Delete hosted zoneaws route53 delete-hosted-zone --id <ZONEID>
Disable auto-renewaws route53domains disable-domain-auto-renew --domain-name mydomain.com

πŸ’° Cost & Notes​

ResourceTypical Cost
Domain~$12/yr (not fixed)
Hosted Zone~$0.50/month
EC2 (t2.micro)Free tier eligible or per-hour cost
Data TransferRegional rates apply

Tip: Use short TTL (e.g., 60 seconds) for faster DNS propagation while testing.