Route 53 Geolocation vs Route 53 Geopriximity vs CloudFront geo-restriction

Geolocation routing

• Use when you want to route traffic based on the location of your users (meaning the location that DNS queries originate from).

Geoproximity routing

• Use when you want to route traffic based on the location of your resources and, optionally, shift traffic from resources in one location to resources in another.

Latency routing

• Use when you have resources in multiple AWS Regions and you want to route traffic to the region that provides the best latency.

CloudFront geo-restriction feature

• Used to prevent users in specific geographic locations from accessing content that you're distributing through a CloudFront web distribution.

• It does not let you choose the resources that serve your traffic based on the geographic location of your users, unlike the Geolocation routing policy in Route 53.