AWS randomly assigns AZ names differently across accounts (docs.aws.amazon.com) 4 points by craigkerstiens 1y ago ↗ HN
[–] awsanswers 1y ago ↗ To prevent the effect of people picking the first zone in the list to launch resources into [–] fhke 1y ago ↗ Exactly this. If they didn’t do this, us-east-1a would be the biggest single point of failure the world has ever seen.
[–] fhke 1y ago ↗ Exactly this. If they didn’t do this, us-east-1a would be the biggest single point of failure the world has ever seen.
[–] gladiatr72 1y ago ↗ Yeah. There is an api call that shows the mapping between a region's az names and the static az id's. I wasn't an early adopter but encountered the random az assignment in 2010.
[–] everfrustrated 1y ago ↗ Been like this for the longest time.Makes sense but a real PITA when using a lot of AWS accounts in an org.In hindsight they should have assigned AZ identifiers to something less sequential.Instead ofeu-east-1, eu-east-2, eu-east-3Do something likeeu-east-s, eu-east-k, eu-east-pwhere the suffixes are the same for everyone. Less bias to choosing -1 then.
5 comments
[ 0.18 ms ] story [ 23.7 ms ] threadMakes sense but a real PITA when using a lot of AWS accounts in an org.
In hindsight they should have assigned AZ identifiers to something less sequential.
Instead of
eu-east-1, eu-east-2, eu-east-3
Do something like
eu-east-s, eu-east-k, eu-east-p
where the suffixes are the same for everyone. Less bias to choosing -1 then.