Routing Policies
~12 min read
Simple, Weighted, Latency-based, Failover, Geolocation, and Multi-value — six ways to decide which endpoint a request goes to.
Routing Policies is a Pro topic
Sign in, then upgrade to Pro or Power to unlock this topic and the full AWS curriculum.
Key points
- •Simple: one endpoint, no rules — the default
- •Weighted: percentage split, great for canary releases and gradual migrations
- •Latency-based: routes by measured network latency, not simple geographic distance
- •Geolocation: routes by user's actual location, for compliance/licensing, not performance
- •Failover: active-passive, health-check-driven — the DR pattern
- •Multi-value: returns several healthy IPs per query for basic distribution and health filtering