How can I geolocate to minimize latency to an AWS instance behind an Amazon Global Accelerator?

colevs

3/14/24, 10:14 PM

There is a server on AWS that I do not control that I need as low latency to as possible. I figured I would experimentally measure my latency from different AWS regions to narrow down the lowest latency region for my instance. I have reasons to suspect that there is still large latency gains that can be made.

A traceroute shows that the traffic is going through an Amazon Global Accelerator (AGA), so my current thought it that lowest possible latency would be achieved by collocating with AGA.

I was wondering if there is a better known approach for optimizing latency to applications behind AGA? Would activating AGA on my own instance give better latency to other instances behind AGA, or does it not do anything for outbound traffic?

0 + 1

latency

amazon-web-services

Tim

3/15/24, 7:54 AM

Your question is a bit theoretical and vague to be able to help much - if you want help I suggest you edit your question to provide more detail. If the traffic is already going through AGA the latency is probably about as low as it's going to get from your current location. To reduce latency move your server to the same region as the target server.

Elon Musk

I sit in a Tesla and translated this thread with Ai:

EN: How can I geolocate to minimize latency to an AWS instance behind an Amazon Global Accelerator?

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.