News for hackers. Stuff that matters.
Re:AWS EC2/RDS Outage in us-east-1 by holykin on Saturday August 31, 2019 @11:32AM (#20846863)
It looks like it was localized to zone D.
Re:AWS EC2/RDS Outage in us-east-1 by tdurden on Saturday August 31, 2019 @11:34AM (#20846886)
Zone designations are account specific; zone D for you is not zone D for me
Re:AWS EC2/RDS Outage in us-east-1 by riffic on Saturday August 31, 2019 @12:10PM (#20847154)
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.
Re:AWS EC2/RDS Outage in us-east-1 by y0y on Saturday August 31, 2019 @12:37PM (#20847329)
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.
Re:AWS EC2/RDS Outage in us-east-1 by turdnagel on Saturday August 31, 2019 @12:39PM (#20847343)
What's the best way of figuring out which zone it could be in my account?
Re:AWS EC2/RDS Outage in us-east-1 by metalrufflez on Saturday August 31, 2019 @02:44PM (#20848076)
Running

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