Hacker News Reader

For folks here, my RDS instances in us-east-1f are doing okay (knock on wood!) Not sure which AZ is suffering most.

My client's Heroku instances are online, thankfully.

Can anyone here speak to their experience with the Ohio region? I'm considering leaning on that more and more.

Your us-east-1f is not the same one as on other accounts. The letter is randomly assigned to the AZ to spread load.

Interesting, never knew that. I guess that is why the announcements never explicitly pointed to a single AZ by name.

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.

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.

Go to your Subnets tab in the EC2 console. You'll see the actual AZ numbers there, vs. the 'random' lettering.

Reply on news.ycombinator.com