DNS
AWS Route 53
- Overview
AWS Route 53 Routing Policies
| Routing Policy | Description | Common Use Case | Supports Health Checks |
|---|---|---|---|
| Simple | Routes traffic to a single resource. No special routing logic. | Single web server or endpoint | No |
| Weighted | Distributes traffic across multiple resources based on assigned weights. | Gradual migration, A/B testing, load distribution | Yes |
| Latency-based | Routes traffic to the region/resource with the lowest latency for the user. | Multi-region deployments for best performance | Yes |
| Failover | Routes traffic to a primary resource, and fails over to a secondary if the primary is unhealthy. | Active-passive failover, disaster recovery | Yes |
| Geolocation | Routes traffic based on the geographic location of the DNS query origin (user’s location). | Compliance, content localization, regional restrictions | Yes |
| Geoproximity | Routes traffic based on the location of resources and optionally shifts traffic between them. | Fine-tuned traffic management across global resources | Yes |
| Multi-value Answer | Returns multiple healthy records (up to 8) at random for each DNS query. | Basic load balancing with health checks | Yes |
| IP-based | Routes traffic based on the originating IP address of the query. | Advanced network segmentation, custom routing logic | Yes |
Key Points:
– Each policy is chosen when creating or editing DNS records.
– Some policies can be combined using Route 53 Traffic Flow for complex routing needs.
– Health checks are supported by most advanced policies, enabling high availability and fault tolerance[1][2][3].
- Watch classroom recording for different routing policy usages and guided creation
