I recently came across this awesome AWS inter-region latency map from Matt Adorjan. It seemed like a gift from heaven. Our engineering team had been working on a solution to build optimized, low latency and reliable connections between AWS VPCs. This was the perfect tool to show what it was they were really looking to solve.
As Matt puts it rather well “I have often been faced with the question of which inter-region transactions will be faced with the most latency. I have been able to find a lot of static examples of previous testing completed, or anecdotal thoughts based on a region’s location. I haven’t been able to find any kind of dynamic, consistently updated, latency monitoring. The goal here is to provide a single source of truth for inter-region AWS region latency”.
AWS inter-region latency map from www.cloudping.co
Our engineering team had already created a worldwide AWS latency map, as a companion to our network performance optimization solution. The AWS latency map shows the latency from three AWS regions to all 600,000 internet prefixes. These regions include Amazon Web Services Frankfurt, Ireland, and North Virginia.
The AWS latency map is generated by continuously pinging all 600,000 internet prefixes, over both the default AWS internet gateway and the ISP partners of Datapath.io. This RTT information is then aggregated into a worldwide AWS latency map.
However, the story doesn’t end with the latency map. Once we have the ping or RTT data for all 600,000 prefixes we then go ahead and plug these into our optimization algorithms. These optimization algorithms are based on BGP and can dynamically re-route internet traffic over the best performing uplink or ISP.
Back to the AWS inter-region latency map. It gave us the perfect baseline to measure the performance of our Inter Region Connect (IRC) solution as compared to the default performance/ latency between different AWS regions. You see, besides reliability and bandwidth heavy connections, one of the reasons for developing the IRC was to provide web services a way to create low latency connections between VPCs in different AWS regions.
Download Inter Region Connect Whitepaper
Peering connections between VPCs in AWS regions
Any web service that needs to optimize the delivery of real-time content and analytics between different VPCs in AWS regions, requires an optimized connection between AWS regions. Companies that work in the Adtech, SaaS, and video streaming space with resources distributed over several AWS regions are especially in need of such a solution.
IRC is built on top of the Datapath.io’s network optimization solution. The network optimization solution gives web services control of the AWS’s network and routing layer by dynamically re-routing traffic over the best performing uplink or ISP partner.
IRC does the opposite. It restricts traffic exchange between VPCs in two different Amazon Web Services regions to one transit provider. Most performance bottlenecks occur because ISPs hand-over un-prioritised traffic to dark corners of the internet. This traffic usually hits an internet highway that is congested.
By ensuring that the traffic exchange between AWS VPCs is restricted to a single transit provider, Datapath.io dramatically reduces the probability of it hitting a congested internet highway.
It also allows Amazon Web Services customers to mix and match criteria like performance and bandwidth to come up with a VPC peering connection that is optimized to their specific requirements.
Read this blog post to learn how to create VPC peering between regions in three simple steps.