AWS Route53 Latency Based Routing
If your application is hosted in multiple AWS Regions, you can improve performance for your users by serving their requests from the AWS Region that provides the lowest latency.
To use latency-based routing, you create latency records for your resources in multiple AWS Regions. When Route 53 receives a DNS query for your domain or subdomain (networknuts.net or aws.networknuts.net), it determines which AWS Regions you’ve created latency records for, determines which region gives the user the lowest latency, and then selects a latency record for that region. Route 53 responds with the value from the selected record, such as the IP address for a web server.
For example, suppose you have ELB load balancers in the US West (Oregon) Region and in the Asia Pacific (Mumbai) Region. You created a latency record for each load balancer. Here’s what happens when a user in London enters the name of your domain in a browser:
- DNS routes the query to a Route 53 name server.
- Route 53 refers to its data on latency between London and the Mumbai region and between London and the Oregon region.
- If latency is lower between the London and Oregon regions, Route 53 responds to the query with the IP address for the Oregon load balancer. If latency is lower between London and the Mumbai region, Route 53 responds with the IP address for the Singapore load balancer.
Latency between hosts on the internet can change over time as a result of changes in network connectivity and routing. Latency-based routing is based on latency measurements performed over a period of time, and the measurements reflect these changes. A request that is routed to the Oregon region this week might be routed to the Mumbai region next week.