AWS's availability zones are unlike Google Clouds AZs, as they are physically meaningfully distant.
A geological or technical event near one AWS AZ is highly unlikely to also affect the others of that region, unless the event is regional (heh) in scale. For Google Cloud, the AZs are effectively co-located buildings (or at least, Eemshaven has 3 GC AZ DCs at < 1km distance from each other), making even local disruptions reasonably likely to impact availability for the whole region.
Yes, that being said, I would expect those same precautions to be taken in all regions, and thus not give a meaningful difference per region, between regions (if that makes sense).
Different regions have different types of worries. Distance and precautions required to deal with redundancy for an earthquake may not be the same as required for a tornado, or hurricane, or flood, etc. In some cases, I imagine elsewhere in the same large city may suffice. In others, maybe it requires 50-100 miles.
Re:AWS inter-region latency chart
by chickenbane on Sunday May 02, 2021 @01:41AM
(#27012616)
You're correct that some Google Cloud zones are in the same physical building. However, the separate zones are designed with independent power, cooling, and networking. So, failure events usually affect only a single zone.
Re:AWS inter-region latency chart
by chrisandchris on Saturday May 01, 2021 @09:05AM
(#27005982)
Isn‘t it interesting how less one knows usually about exact specs of the Cloud?
Us-east-1 aws buildings are within couple miles too
us-east-1 is a very special region. All of Amazon.com runs/ran there for a long time. And a lot of global features of AWS itself run there too.
The chart doesn't show AZ data, which seems like an important piece of this puzzle.
Perhaps OP can answer. The AZ ID[0], as opposed to the name, does identify a specific AZ location, so certainly possible to measure AZ-to-AZ latencies.
[0] https://docs.aws.amazon.com/ram/latest/userguide/working-wit...
Ie, I would not have expected eu-central-1/eu-central-1 to be 1.68ms, and us-east-2/us-east-2 is 8.26ms (almost 5x)