4 ms·
I thought that AWS availability zones were intentionally not canonically named to prevent everyone from adding stuff to AZ “A”. So my us-east-1 zone “A” might b
by brasic 4y ago
I thought that AWS availability zones were intentionally not canonically named to prevent everyone from adding stuff to AZ “A”. So my us-east-1 zone “A” might be your “B”.
But that system breaks down here when you need to know whether you are in an affected zone. Is there a way to map an account’s AZ name to the canonical one which apparently exists?
- nathanwh 4y agoYep! https://docs.aws.amazon.com/ram/latest/userguide/working-with-az-ids.html https://docs.aws.amazon.com/ram/latest/userguide/working-wit...
- fdr 4y agoThey gave up on that, now there's an extra "zone ID" you can read that maps to an absolute address. They used to be extremely cagey about giving out those mappings for your account. Examples about how these relate: https://stackoverflow.com/questions/63283340/aws-map-between-availability-zone-and-zone-name https://stackoverflow.com/questions/63283340/aws-map-between... I'm also pretty sure that GCP's identifiers are absolute (and this time, throughout) as well, since their documentation (which renders the same in incognito mode or whatever) makes reference to what zones have what microarchitectures and instance types.
- packetslave 4y agoThe mapping from AZ Name (account-specific) to AZ ID (global) shows up on the EC2 overview page in the dashboard.
- res0nat0r 4y agoThis is true, at the AWS account level. us-east-2a for my account may map to the internal use2-az1, but in your account us-east-2a may map internally to use2-az2.