Networking and Content Delivery
CoreAmazon Route 53
Authoritative DNS, domain registration, health checks, and routing policies for directing clients to endpoints.
Key points
- Route 53 returns DNS answers; it does not proxy or cache application content.
- Routing policies such as weighted, latency, geolocation, multivalue, and failover serve different business and traffic goals.
- Health-based routing depends on suitable checks and healthy, ready endpoint capacity; resolver TTLs affect change observation.
Best-known use cases
- Route users to regional endpoints.
- Implement DNS failover between healthy application endpoints.
What candidates often confuse it with
- Route 53 routes via DNS; Global Accelerator provides static anycast IPs and proxies supported traffic.
- Route 53 selects endpoints; ELB distributes traffic among targets.
Key takeaway
Choose Route 53 for DNS-based routing and health failover, while accounting for resolver caching.
Related services
- Amazon CloudFront
- AWS Global Accelerator
- Elastic Load Balancing (ELB)
Relevant exam tasks
- D2.2
- D3.4
- D4.4