News for hackers. Stuff that matters.
Re:AWS EC2/RDS Outage in us-east-1 by whalesalad on Saturday August 31, 2019 @04:32PM (#20848639)
Interesting, never knew that. I guess that is why the announcements never explicitly pointed to a single AZ by name.
Re:AWS EC2/RDS Outage in us-east-1 by zifnab06 on Saturday August 31, 2019 @05:21PM (#20848845)
Essentially everyone picks "a" because it's the first az. There's some internal mapping to "your az a is actually datacenter q". You can kind of figure out which AZs match across accounts if you've got enough accounts you can send traffic between.

I've been told that the "a" AZ you get was the least populated at object creation time (ie the first time you make an object that lives in an az), but I don't know how valid that is.

Re:AWS EC2/RDS Outage in us-east-1 by whalesalad on Saturday August 31, 2019 @05:40PM (#20848938)
Aside from spinning up an EC2 node in each AZ and doing ping or tracing tests I wonder if there is a quick-n-dirty way to map AZ’s between different AWS accounts. I’ve never had to approach that scenario (cross account, low latency requirements) but in the future I’ll keep this in mind.
Re:AWS EC2/RDS Outage in us-east-1 by cthalupa on Saturday August 31, 2019 @08:57PM (#20849835)
Go to your Subnets tab in the EC2 console. You'll see the actual AZ numbers there, vs. the 'random' lettering.