News for hackers. Stuff that matters.
Re:More Than DNS: The 14 hour AWS us-east-1 outage by easton on Wednesday October 29, 2025 @10:08PM (#45755665)
They used to do that (so that everyone picking 1a wouldn’t actually route traffic to the same az), but at some point they made it so all new accounts had the same AZ labels to stop confusing people.

The services that fail on AWS’ side are usually multi zone failures anyway, so maybe it wouldn’t help.

I’ve often wondered why they don’t make a secret region just for themselves to isolate the control plane but maybe they think dogfooding us-east-1 is important (it probably wouldn’t help much anyway, a meteor could just as easily strike us-secret-1).

Re:More Than DNS: The 14 hour AWS us-east-1 outage by nevon on Thursday October 30, 2025 @05:57AM (#45758162)
This is not exactly true. The az names are indeed randomized per account, and this is the identifier that you see everywhere in the APIs. The difference now is that they also expose a mapping from AZ name (randomized) to AZ id (not randomized), so that you can know that AZ A in one account is actually in the same datacenter as AZ B in a different account. This becomes quite relevant when you have systems spread across accounts but want the communication to stay zonal.
Re:More Than DNS: The 14 hour AWS us-east-1 outage by waiwai933 on Thursday October 30, 2025 @08:02AM (#45759091)
You're both partially right. Some regions have random mapping for AZs; all regions since 2012 have static AZ mapping. https://docs.aws.amazon.com/global-infrastructure/latest/reg...
Re:More Than DNS: The 14 hour AWS us-east-1 outage by nevon on Thursday October 30, 2025 @08:17AM (#45759192)
Oh wow. Thanks for telling me this. I didn't know that this was different for different regions. I just checked some of my accounts, and indeed the mapping is stable between accounts for for example Frankfurt, but not Sydney.