AWS Networking: Amazon Route 53 Study Guide

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 names like www.example.com into numeric IP addresses like 192.0.2.1.

The Real-World Analogy: Think of Route 53 as the ultimate GPS and Global Phonebook. When you want to visit a friend (website), you look up their name in the book. Route 53 not only gives you the address but also checks if they are home (Health Checks) and directs you to the house closest to you to save time (Latency Routing).

Core Concepts and Features

1. Domain Registration

Route 53 allows you to register domain names (e.g., .com, .net, .org). It acts as a registrar, managing the administrative aspects of domain ownership.

2. Hosted Zones

Public Hosted Zones: Determine how traffic is routed on the internet.
Private Hosted Zones: Determine how traffic is routed within one or more Amazon VPCs without exposing DNS data to the public internet.

3. Record Types

While Route 53 supports standard DNS records (A, AAAA, CNAME, MX, etc.), the Alias Record is a key SAA-C03 topic. Unlike a CNAME, an Alias record can point to the “Zone Apex” (the naked domain, like example.com) and is specifically designed to point to AWS resources like ELBs, CloudFront distributions, or S3 buckets.

Routing Policies: The Heart of Route 53

Policy	Use Case	Exam Key Phrase
Simple	Single resource performing a function.	“Standard DNS,” “No health checks.”
Weighted	Split traffic between multiple resources (A/B testing).	“Percentage-based,” “Blue/Green deployment.”
Latency	Route based on lowest network latency for the user.	“Performance,” “User experience,” “Network delay.”
Failover	Active-Passive disaster recovery.	“Disaster recovery,” “Health check based.”
Geolocation	Route based on user’s physical location (continent/state).	“Localization,” “Compliance,” “Regional content.”
Geoproximity	Route based on resource location + “Bias” to shift traffic.	“Traffic flow,” “Complex geographical shifts.”
Multi-value Answer	Return up to 8 healthy records randomly.	“Simple load balancing,” “Health check integration.”

Hybrid Cloud and Route 53 Resolver

For SAA-C03, understand how to bridge on-premises and AWS DNS:

Inbound Endpoints: Allows on-premises networks to resolve DNS queries for AWS resources.
Outbound Endpoints: Allows AWS resources to resolve DNS queries for on-premises domains.

Decision Matrix / If–Then Guide

If you need to route to a naked domain (example.com) to an ELB… Then use an Alias Record.
If you need to perform A/B testing or canary releases… Then use Weighted Routing.
If you must comply with data sovereignty or local laws… Then use Geolocation Routing.
If you want to minimize network delay for global users… Then use Latency Routing.
If you need a cost-effective DR strategy… Then use Failover Routing with Health Checks.

Exam Tips and Gotchas

Alias vs. CNAME: Always prefer Alias for AWS resources. It’s free (for AWS resources) and works at the Zone Apex. CNAMEs cannot be at the Zone Apex.
Health Checks: Route 53 can check the health of an endpoint via HTTP, HTTPS, or TCP. If a resource is unhealthy, Route 53 removes it from DNS responses.
TTL (Time to Live): High TTL = faster DNS resolution (cached longer) but slower updates. Low TTL = faster updates (propagation) but higher query costs. Note: Alias records do not have a user-configurable TTL for certain AWS resources.
Private DNS: To use Private Hosted Zones, you must enable enableDnsHostnames and enableDnsSupport in your VPC settings.
DNSSEC: Route 53 supports DNSSEC to protect against DNS spoofing/man-in-the-middle attacks.

Topics covered:

Summary of key subtopics covered in this guide:

DNS Fundamentals and Domain Registration
Public vs. Private Hosted Zones
Alias Records vs. CNAME Records
The 7 Routing Policies (Simple, Weighted, Latency, etc.)
Health Checks and Failover mechanisms
Route 53 Resolver (Inbound/Outbound Endpoints)
VPC DNS requirements (enableDnsHostnames/Support)

Amazon Route 53 Architecture Infographic

Ecosystem

Service Integration

IAM: Control who can change DNS records.
CloudWatch: Monitor health check status and trigger alarms.
Shield: Route 53 provides built-in DDoS protection.
VPC: Private DNS resolution for internal services.

Performance

Global Edge Network

Route 53 uses a global network of DNS servers at AWS Edge Locations to provide low-latency responses worldwide.

Use Case: Use Latency Routing to direct Tokyo users to ap-northeast-1 and London users to eu-west-2 automatically.

Cost Optimization

Smart Savings

Alias Records: Queries to Alias records for AWS resources (ELB, S3, CloudFront) are free of charge.
Health Checks: Charged per check; use sparingly for non-critical endpoints.
Visual Editor: Use Traffic Flow for complex routing visual management ($50/policy/month).

Production Use Case: Disaster Recovery

A company hosts their primary site in us-east-1. They set up a Failover Routing Policy. Route 53 monitors the health of the primary Load Balancer. If it fails, Route 53 automatically updates DNS to point to a static “Maintenance” page hosted on Amazon S3 in us-west-2.