Routing Policies
Routing Policies define how Route 53 respond to DNS queries.
There are 7 type of policies
Simple
Weighted
Failover
Latency based
Geolocation
Multi Value Answer
Geoproximity
(1) Simple
It will respond only single resource. We can specify multiple values in same record but client will choose only one random value from these and If we use Alias then it will choose only one AWS resource. This policy does not support for health check.
(2) Weighted
In this strategy we will apply weighted to each of destination so the traffic will go to destination that has a highest weighted . Weighted is similar to the number of traffic in percentage units. Also It can be associated with Health Checks feature.
Usecase
Load balancing between region
Good To Know:
Asign a weightof 0 to a record to stop sending traffic to a resource
If all records have weight of 0, then all records will be returned equality.
(3) Failover
It will has 2 kind of record we need to set one for primary instance and another for secondary instance. When Primary instance is failed then it will return Secondary instead. This strategy require to have Health Check.
(4) Latency Based
It redirects to the resource that has the least latency close to user. Latency is based on traffic between users and AWS region.
e.g :
Germany users may be directed to the US (If that is the lowest latency). Also It can be associated with Health Checks feature.
(5) Geolocation
This routing is baed on user location and If it did not find the location of user , then it will return default record instead (No match on location). Also It can be associated with Health Checks feature.
If you use the VPN, your location is based on that VPN.
Usecase
Restrict content on location
Website localization
(6) Multi Value
It will return multiple resources. Also It can be associated with Health Checks feature.
(7) Geoproximity
In the same location we have mutiple resource there but we will set the bias to one of these resources then the traffic mostly go to that resoruce.
Last updated
