3 ms·
I've been using AWS for years and this is the first I've ever heard of this. All I can say is "WHAAAAAAT?!" You've made me question my reality. Take an upvote
by danielhunt 10y ago
I've been using AWS for years and this is the first I've ever heard of this.
All I can say is "WHAAAAAAT?!"
You've made me question my reality. Take an upvote for that alone.
- aidos 10y agoI'm glad I could make what is otherwise a bad time to be looking after servers a little more enjoyable. I myself was in the middle of a release when all this happened. "I'll just release this thing" I said, "will only take 20 minutes" I said....
- misframer 10y agoIt's in the documentation [0]. An Availability Zone is represented by a region code followed by a letter identifier; for example, us-east-1a. To ensure that resources are distributed across the Availability Zones for a region, we independently map Availability Zones to identifiers for each account. For example, your Availability Zone us-east-1a might not be the same location as us-east-1a for another account. There's no way for you to coordinate Availability Zones between accounts. [0] http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-regions-availability-zones.html#concepts-regions-availability-zones http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-reg...