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

Last updated: 2019-05-23

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

Short description

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.


Create a geoproximity routing traffic policy

1.    Create a traffic policy.

2.    For Start point, choose A: IP address in IPv4 format as the DNS type.

3.    Choose Connect to, 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 (Amazon 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.    Choose Connect to, 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 +short with the DNS name of your traffic policy. Use +subnet in your command to test routing from specific IP address locations.

Example command:

dig +subnet=<subnet> +short 

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

Did this article help?

Do you need billing or technical support?