Hacker News new | ask | show | jobs
by holykin 2481 days ago
It looks like it was localized to zone D.
2 comments
tdurden 2481 days ago
Zone designations are account specific; zone D for you is not zone D for me
link
riffic 2481 days ago
The affected AZ appears to be use1-az6. You can map "your" AZ name (us-east-1c, us-east-1d, etc.) to the actual, canonical name of the AZ in the 'Subnets' tab on the VPC console.
link
y0y 2481 days ago
What makes you say use1-az6 is the culprit? I only ask because none of our workloads in az6 have experienced any issues. ....yet. We run critical workloads across 3 AZs thankfully, but still.
link
turdnagel 2481 days ago
What's the best way of figuring out which zone it could be in my account?
link
metalrufflez 2481 days ago
Running

  aws ec2 describe-availability-zones --region us-east-1 --output text
link