Please enable JavaScript.
Coggle requires JavaScript to display documents.
Route 53 Routing Policies - Coggle Diagram
Route 53 Routing Policies
Simple
Typically, route traffic to a single resource
Can’t be associated with Health Checks
Can specify multiple values in the same record
Weighted
Control the % of the request that go to each specific resource
Can be associated with Health Checks
Use case: Load balancing between regions, testing new application versions
Latency-based
Redirect to the resource that has the least latency close to us
Can be associated with Health Checks
Helpful when latency for users is a priority
Failover
Geolocation
Different from Latency-based
Based on user location
Use case: Website localization, restrict content distribution, load balancing
Geoproximity Routing Policy
Route traffic to your resources based on the geographic location of users and resources
Ability to shift more traffic to resources based on the defined
bias
Helpful to shift traffic from one region to another by increase the
bias
Multi Value
Use when routing traffic to multiple resources
Can be associated with Health Checks