Don't Pick AWS us-east (if you can)

After large AWS incidents, they post a post-mortem on this list.

As of today, there are 16 outages that AWS considers as significant.

Of these 16 outages, 8 were from the us-east regions. Four of those eight were in us-east-1.

If you were starting today and can afford it, I’d recommend using the us-west regions.

EC2 instances and everything in costs more in general in us-west. However, in the future, you might never need to engineer your workloads for multiple regions.

Summary of the AWS Lambda Service Event in Northern Virginia (US-EAST-1) Region, June 13, 2023
Summary of the AWS Service Event in the Northern Virginia (US-EAST-1) Region, December 7, 2021
Summary of AWS Direct Connect Event in the Tokyo (AP-NORTHEAST-1) Region, September 2, 2021
Summary of the Amazon Kinesis Event in the Northern Virginia (US-EAST-1) Region, November 25, 2020 
Summary of the Amazon EC2 and Amazon EBS Service Event in the Tokyo (AP-NORTHEAST-1) Region, August 23, 2019
Summary of the Amazon EC2 DNS Resolution Issues in the Asia Pacific (Seoul) Region (AP-NORTHEAST-2), November 22, 2018.
Summary of the Amazon S3 Service Disruption in the Northern Virginia (US-EAST-1) Region, February 28, 2017.
Summary of the AWS Service Event in the Sydney Region, June 4, 2016.
Summary of the Amazon DynamoDB Service Disruption and Related Impacts in the US-East Region, September 20, 2015.
Summary of the Amazon EC2, Amazon EBS, and Amazon RDS Service Event in the EU West Region, August 7, 2014.
Summary of the Amazon SimpleDB Service Disruption, June 13, 2014.
Summary of the December 17th event in the South America Region (SA-EAST-1), December 17, 2013.
Summary of the December 24, 2012 Amazon ELB Service Event in the US-East Region, December 24, 2012.
Summary of the October 22, 2012 AWS Service Event in the US-East Region, October 22, 2012.
Summary of the AWS Service Event in the US East Region, June 29, 2012.
Summary of the Amazon EC2 and Amazon RDS Service Disruption in the US East Region, April 21, 2011

Master GitHub Actions with a Senior Infrastructure Engineer

As a senior staff infrastructure engineer, I share exclusive, behind-the-scenes insights that you won't find anywhere else. Get the strategies and techniques I've used to save companies $500k in CI costs and transform teams with GitOps best practices—delivered straight to your inbox.

Not sure yet? Check out the archive.

Unsubscribe at any time.