AWS Network Services: Route 53, DNS, and Global Content Delivery

This study guide covers the fundamental networking services within the AWS ecosystem required for the SAA-C03 exam, focusing primarily on the Domain Name System (DNS), Amazon Route 53, and Amazon CloudFront.

---

Learning Objectives

After studying this material, you should be able to:

• Explain the hierarchy of DNS and how name resolution works.
• Identify and configure key DNS record types (A, AAAA, CNAME, MX, NS, SOA).
• Distinguish between different Route 53 routing policies and their specific use cases.
• Understand the role of Amazon CloudFront in reducing latency through edge caching.
• Design highly available and cost-optimized network architectures using health checks and failover routing.

Key Terms & Glossary

• FQDN (Fully Qualified Domain Name): The complete domain name for a specific host on the internet (e.g., www.example.com.).
• TLD (Top-Level Domain): The last segment of a domain name (e.g., .com, .org, .edu).
• SLD (Second-Level Domain): The specific name registered to an owner (e.g., amazon in amazon.com).
• Hosted Zone: A container for records that defines how you want to route traffic for a domain and its subdomains.
• Edge Location: A site that CloudFront uses to cache copies of your content for faster delivery to users at any location.
• Alias Record: An AWS-specific DNS record that points to AWS resources (like an ELB or S3 bucket) rather than an IP address.

The "Big Idea"

DNS is the "phonebook" of the internet, translating human-readable names into machine-readable IP addresses. However, in AWS, Route 53 is more than just a phonebook; it is an intelligent traffic cop. By utilizing routing policies, Route 53 can decide where to send a user based on health, proximity, or cost, ensuring that the network architecture is resilient, high-performing, and geographically optimized.

Formula / Concept Box

Hierarchical Outline

1. DNS Fundamentals
   • Structure: Root → TLD → SLD → Subdomain.
   • Resolution: Iterative vs. Recursive queries.
2. Amazon Route 53
   • Registration: Buying and managing domain names.
   • Hosted Zones: Public (internet-facing) vs. Private (internal VPC traffic).
   • Routing Policies: The logic used to respond to DNS queries.
3. Content Delivery & Performance
   • CloudFront: Global CDN using Edge Locations and Points of Presence (PoP).
   • Global Accelerator: Uses the AWS Global Network to optimize the path from users to applications.
4. Network Cost & Optimization
   • VPC Endpoints: Reducing data transfer costs by keeping traffic inside the AWS network.
   • NAT Gateways: Managing outbound internet access for private subnets cost-effectively.

Visual Anchors

DNS Resolution Flow

Global Traffic Distribution

Definition-Example Pairs

• Weighted Routing: Distributes traffic across multiple resources in proportions that you specify.
  • Example: Testing a new software version by sending 10% of traffic to the new fleet (Canary release).
• Latency Routing: Routes traffic to the AWS region that provides the lowest latency for the user.
  • Example: A user in Tokyo is automatically directed to the ap-northeast-1 region rather than us-east-1 to improve page load speed.
• Failover Routing: Uses a primary and secondary resource; traffic only goes to secondary if the primary is unhealthy.
  • Example: Configuring a static "Maintenance" page on S3 that users only see if the main Application Load Balancer fails a health check.

Worked Examples

Problem: Selecting the Right Routing Policy

Scenario: A company has a global application deployed in us-east-1 (Virginia) and eu-central-1 (Frankfurt). They want to ensure that users always experience the fastest response times, but if one region goes down, all traffic should automatically shift to the healthy region.

Step-by-Step Solution:

1. Analyze the Requirement: We need both performance (speed) and availability (failover).
2. Select Primary Logic: Use Latency Routing to ensure users hit the closest region by default.
3. Add Resilience: Configure Health Checks for the endpoints in both regions.
4. Integration: Route 53 Latency records can be associated with health checks. If the Frankfurt region fails its health check, Route 53 will stop returning that record and only return the healthy Virginia record, effectively performing a failover.

[!TIP] Alias records are preferred over CNAMEs for the "Zone Apex" (e.g., example.com without the www). CNAMEs are not allowed at the apex by DNS standards, but AWS Alias records solve this.

Checkpoint Questions

1. Which DNS record type is used to map a domain name to an IPv6 address?
2. What is the main difference between Geolocation and Geoproximity routing?
3. Why would a Solutions Architect choose an Alias record over a CNAME when pointing to an ELB?
4. True or False: CloudFront can be used to serve both static and dynamic content.
5. How do Health Checks interact with Route 53 routing policies?

▶Click to expand answers

1. AAAA Record.
2. Geolocation routes based on the user's physical location (e.g., all users in France). Geoproximity routes based on the distance between the user and the resource, allowing you to "bias" traffic toward specific regions.
3. Alias records are free of charge for AWS resources and can be used at the Zone Apex.
4. True. While often used for static caching, CloudFront optimizes the delivery of dynamic content via connection pooling and optimized paths to the origin.
5. If a health check fails, Route 53 removes the unhealthy resource from the DNS response until it passes again, enabling automatic failover.