Amazon Route 53 expands geoproximity routing
Starting today, Amazon Route 53 supports geoproximity routing as an additional routing policy for DNS records in public and private hosted zones. Geoproximity routing improves application responsiveness for your end users and helps organizations apply data residency preferences by routing traffic to the geographically nearest resource. With this release, you can add geoproximity routing to your DNS records via the Route 53 Console, API, SDK, and CLI. E-commerce, media and entertainment, information technology, and social media are just some of the many industries with a need for delivering highly responsive web and mobile digital experiences. Now, you can quickly improve the experience of users anywhere in the world simply by configuring each application endpoint to use geoproximity routing. You can also expand or reduce the geographic area from which traffic is routed to a resource by making changes to a record’s bias value, allowing you to establish geographic boundaries that are best served by your infrastructure resources. Route 53 previously offered geoproximity routing only within traffic flow, but is now expanding its availability to the entire DNS service based on customer demand by providing geoproximity routing as an option alongside the other [routing policies](https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/routing-policy.html). Geoproximity routing is available globally, except in AWS GovCloud and Amazon Web Services in China. Route 53 pricing information can be found [here](https://aws.amazon.com/route53/pricing/). To learn more about how to use geoproximity routing, visit our [documentation](https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/routing-policy-geoproximity.html) and [this blog post](https://aws.amazon.com/blogs/networking-and-content-delivery/managing-global-aws-local-zones-applications-with-amazon-route53-geoproximity-routing/).