2

Is it possible to use Amazon Route 53 Geolocation routing policy with a custom subnet instead of the available Continent/Country location?

I have requirements to go a bit more in depth than country level. Subnet level.

1 Answers1

3

No, it is not possible. According to http://docs.aws.amazon.com/Route53/latest/DeveloperGuide/routing-policy.html#routing-policy-geo Geolocation routing policy only supports a predefined list of continents, countries and states.

  • Was well aware of those specs, but I was hoping I've missed something, somewhere. Since they go through the trouble of mapping IP addresses to regions so you can route based on the region, it would be a no brainer to allow one to route directly based on a subnet. – Mihai Caracostea Dec 19 '15 at 23:33
  • Looks to me it better be done by the app serving requests, based on the remote address. Or Nginx reverse proxy, similarly to http://www.cyberciti.biz/faq/nginx-redirect-backend-traffic-based-upon-client-ip-address/. – Evgeny Goldin Dec 20 '15 at 00:49
  • Well, the app serving requests is on the server which Route 53 should be pointing to. – Mihai Caracostea Dec 20 '15 at 00:53
  • Right. What I meant since Route 53 does not provide geo routing policy by the subnet - I'd implement it on the server side, serving or redirecting to a different content based on the remote address. – Evgeny Goldin Dec 20 '15 at 02:31