Amazon Route 53 traffic flow now supports geoproximity routing for AWS Local Zones
Starting today, Route 53 geoproximity routing can be used with AWS Local Zones in Route 53 traffic flow to reduce latency for end users connecting to applications running in their nearest Local Zone. With this release, you can improve application performance for latency-sensitive workloads by routing traffic within the same geographic area as that of Local Zone infrastructure.
Starting today, Route 53 geoproximity routing can be used with AWS Local Zones in Route 53 traffic flow to reduce latency for end users connecting to applications running in their nearest Local Zone. With this release, you can improve application performance for latency-sensitive workloads by routing traffic within the same geographic area as that of Local Zone infrastructure.
Online gaming, media and entertainment, healthcare, and the public sector are just some of the many industries with low latency requirements, local data processing, or data residency preferences. These customers have asked for an easy, fast way to route end user traffic to Local Zones applications residing in the same metropolitan area. Now, Route 53 traffic flow includes Local Zones as destinations for such traffic, improving the user experience, enabling compliance with data residency regulations, and helping to better utilize edge compute infrastructure.
Geoproximity routing support for Local Zones in traffic flow is available globally, except in AWS GovCloud (US) and Amazon Web Services China. Route 53 pricing information can be found here. To learn more, visit the Amazon Route 53 product page or see our documentation.