Geolocation and Geoproximity Routing policy

Geolocation Routing

Core idea: Route traffic based on where the user is located.

You define rules like: "Users from Germany → Server A", "Users from France → Server B"
Location can be a Continent, Country, or US State
If no location matches, the Default record handles the request
Always create a Default record — without it, unmatched users get no response

Use cases: Show region-specific content, restrict access by country, regional load balancing

Core idea: Route traffic based on how close the user is to a resource — and shift that boundary using bias.

Bias lets you expand or shrink a resource's "serving area":

Bias Value	Effect
1 to 99	Expand the area — more traffic goes here
-1 to -99	Shrink the area — less traffic goes here
0	Default — split by distance

Both regions, Bias = 0 — traffic splits evenly at the midpoint:

us-east-1 Bias = 50 — east's boundary shifts west, pulling more users:

The orange boundary line moves. East gets more traffic even from users closer to the west.

Geoproximity requires Route 53 Traffic Flow to be enabled.