Just don't use US-EAST-1 as your region.
1. https://en.wikipedia.org/wiki/Timeline_of_Amazon_Web_Service...
* It's the largest region (ever had an unexpected scaling bug?).
* It has more legacy stuff lying around. For example, old regions have EC2 Classic, while new regions are VPC only.
* There are more customers there. More whales, more use cases.
Most AWS teams explicitly try not to deploy to us-east-1 first, but because us-east-1 is so different on so many dimensions, it is more likely to have issues that dont manifest elsewhere.
(Source: An AWS Engineer)
That doesn't make sense - why would they do maintenance in their largest (and oldest) region first? I'd expect them to roll out changes to smaller regions first so problems will affect fewer users.
I think the more likely explanation is that it's their largest (and oldest) region.
> Between 9:21 AM and 2:36 PM PDT we experienced increased query failures and latency in the US-EAST-1 Region. The issue has been resolved and the service is operating normally.
> The issue with the Data Catalog APIs started with a software update in the US-EAST-1 Region that completed at 9:21 AM PDT. The software update was immediately rolled back[...]
