How do I configure geoproximity routing for traffic using the Amazon Route 53 console?

You can use geoproximity routing in the Route 53 console to route traffic based on the physical distance between your users and your resources. You can also configure the size of a geographic Region from which Route 53 routes traffic to a resource by specifying a bias for the Region.

Note: You must use Route 53 traffic flow to use a geoproximity routing policy.

To create a geoproximity routing policy using the AWS Command Line Interface (AWS CLI) instead, see How do I configure geoproximity routing in Route 53 using the AWS CLI?

Create a geoproximity routing traffic policy

  1. Follow the steps in Creating a Traffic Policy to create your policy.
  2. For Start point, choose A: IP address in IPv4 format as the DNS type.
  3. Open the Connect to menu, and then choose Geoproximity rule.
  4. 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 (EC2) Region where your endpoint is located, such as US East (N. Virginia).
  5. Optional: For Bias, enter a number, or drag the slider to the bias value you want.
  6. Optional: Under Health checks, select or clear the check box to Evaluate target health. Then, select a health check to associate with the record.
  7. Open the Connect to menu, and then choose New endpoint.
  8. For Type, choose Value.
  9. For Value, enter the IP address of your endpoint.
  10. For each additional endpoint you want to add, choose Add another geoproximity location, and then follow steps 4-9 again.
  11. Choose Create traffic policy.

Create a policy record for your traffic policy

Follow the steps in Creating Policy Records to create your policy record. Be sure to choose the traffic policy you just created for the Traffic policy record.

Test geoproximity routing

Test if Route 53 routes traffic to the correct endpoint.

To test the DNS response using the Route 53 console, see Checking DNS Responses from Route 53.

To test the DNS response in a Linux terminal, use dig (version of 9.11 or later). Open a terminal and use dig +trace with the DNS name of your traffic policy. Use +subnet in your command to test routing from specific IP address locations.

Example command:

dig geoproximity-test.example.com +subnet=<subnet> +short 

where
<subnet> is the Client Subnet (or the Client) address with the mask in the format of X.X.X.X/X

Did this page help you? Yes | No

Back to the AWS Support Knowledge Center

Need help? Visit the AWS Support Center

Published: 2018-08-24