7 ms·

I'm seeing issues in 2a but not 2b. Anyone having issues in 2b?

NovemberWhiskey 4y ago
Just FYI; availability zone names in AWS are randomized between accounts - your "a" can be someone else's "f" Physical identifiers for availability zones are like "use2-az1", ref. https://docs.aws.amazon.com/ram/latest/userguide/working-with-az-ids.html https://docs.aws.amazon.com/ram/latest/userguide/working-wit...
bradyd 4y ago
Availability zones are not guaranteed to have the same name across accounts (ie. us-east-2a in one account might be us-east-2d in another). You would need to use the AZ-ID to determine if they are the same. https://docs.aws.amazon.com/prescriptive-guidance/latest/patterns/use-consistent-availability-zones-in-vpcs-across-different-aws-accounts.html https://docs.aws.amazon.com/prescriptive-guidance/latest/pat...
silverlyra 4y ago
AWS availability zones are randomly shuffled for each AWS account – your us-east-2a won't (necessarily) be the same as another user's (or even another account in the same organization): https://docs.aws.amazon.com/ram/latest/userguide/working-with-az-ids.html https://docs.aws.amazon.com/ram/latest/userguide/working-wit... You'll need to see which availability zone ID (e.g., use2-az3) corresponds to each zone in your account: https://aws.amazon.com/premiumsupport/knowledge-center/vpc-map-cross-account-availability-zones/ https://aws.amazon.com/premiumsupport/knowledge-center/vpc-m... edit: AWS identified this as a power loss in a single zone, use2-az1.
- blahyawnblah 4y ago
  I wonder if this is done because people have a tendency or something to always create resources in 'A' (or some other AZ) and this helps spread things around. And if I would have read the page the link points to better, that's exactly the reason
NightMKoder 4y ago
AWS availability zones (so like us-west-2b rather than us-west-2) are not the same between accounts. us-west-2b for you is something different than us-west-2b for everyone else.

Just FYI; availability zone names in AWS are randomized between accounts - your "a" can be someone else's "f" Physical identifiers for availability zones are like "use2-az1", ref. https://docs.aws.amazon.com/ram/latest/userguide/working-with-az-ids.html https://docs.aws.amazon.com/ram/latest/userguide/working-wit...

bradyd 4y ago

Availability zones are not guaranteed to have the same name across accounts (ie. us-east-2a in one account might be us-east-2d in another). You would need to use the AZ-ID to determine if they are the same. https://docs.aws.amazon.com/prescriptive-guidance/latest/patterns/use-consistent-availability-zones-in-vpcs-across-different-aws-accounts.html https://docs.aws.amazon.com/prescriptive-guidance/latest/pat...

silverlyra 4y ago

AWS availability zones are randomly shuffled for each AWS account – your us-east-2a won't (necessarily) be the same as another user's (or even another account in the same organization): https://docs.aws.amazon.com/ram/latest/userguide/working-with-az-ids.html https://docs.aws.amazon.com/ram/latest/userguide/working-wit... You'll need to see which availability zone ID (e.g., use2-az3) corresponds to each zone in your account: https://aws.amazon.com/premiumsupport/knowledge-center/vpc-map-cross-account-availability-zones/ https://aws.amazon.com/premiumsupport/knowledge-center/vpc-m... edit: AWS identified this as a power loss in a single zone, use2-az1.

blahyawnblah 4y ago
I wonder if this is done because people have a tendency or something to always create resources in 'A' (or some other AZ) and this helps spread things around. And if I would have read the page the link points to better, that's exactly the reason

NightMKoder 4y ago

AWS availability zones (so like us-west-2b rather than us-west-2) are not the same between accounts. us-west-2b for you is something different than us-west-2b for everyone else.