How do I configure geoproximity routing using the Route 53 console?
Last updated: 2022-03-04
How do I configure geoproximity routing using the Amazon Route 53 console?
Note: You must use Route 53 traffic flow to use a geoproximity routing policy.
Create a traffic policy with geoproximity routing
- Create a traffic policy.
- For Start point, choose the desired record type, such as A or MX.
- For Connect to, choose Geoproximity rule.
- Choose your Endpoint Location. If you choose Custom, you must enter the location’s latitude and longitude Coordinates. Otherwise, choose the Amazon Elastic Compute Cloud (Amazon EC2) Region where your endpoint is located, such as US East (N. Virginia).
- (Optional) For Bias, enter the desired bias value. Choose Show geoproximity map for a visual representation of the effects the bias that you're configuring.
- (Optional) Under Health checks, select or clear Evaluate target health. Then, select a health check to associate with the record.
- For Connect to, and choose New endpoint.
- For Type, choose Value.
- For Value, enter the IP address of your endpoint.
- For each additional endpoint, choose Add another geoproximity location, and then repeat steps 4-9.
- Choose Create traffic policy.
(Optional) Create a policy record
Using a policy record, you can route traffic from the internet to the resources specified in your traffic policy. When you create a policy record, you specify the traffic policy to use and the hosted zone where it's created. For more information, see Creating policy records.
(Optional) Test your geoproximity routing policy
To test the DNS response using the Route 53 console, see Checking DNS responses from Route 53.
Important: Route 53 uses the edns-client-subnet extension of EDNS0 to improve the accuracy of the responses returned.
For Route 53 to use EDNS0 when making routing decisions, the resolver used to perform the query must support EDNS0. If the resolver doesn't support EDNS0, then the IP address of the resolver is used to make a routing decision. If the resolver supports EDNS0, then a truncated version of the client IP address making the original request is passed to Route 53 and used to make a decision.
When testing how Route 53 is responding to geoproximity queries, you must determine if the resolver supports EDNS0. For more information, see How can I determine if my public DNS resolver supports the EDNS Client Subnet extension?