3 ms·
It seems like a vanishingly small chance that us-east-1 will have a total meltdown across its 6 AZ's. But us-east-1 appears to be the most problematic region (
by Johnny555 5y ago
It seems like a vanishingly small chance that us-east-1 will have a total meltdown across its 6 AZ's.
But us-east-1 appears to be the most problematic region (instance launch issues, API issues, etc), so for that reason alone, I wouldn't build a new deployment there. If I wanted proximity to the east coast, I'd probably go with us-east-2 (Ohio) with a backup in ca-central-1.
I'm not worried about surviving a meteor strike or Carrington Event, not much point in keeping a company alive when its employees and customers are struggling to survive.
- bigiain 5y ago> It seems like a vanishingly small chance that us-east-1 will have a total meltdown across its 6 AZ's. Yeah - it's not the sort of thing that you expect to happen often, it's not like it went down twice last month or anything... https://thestack.technology/aws-us-east-1-wobbles-for-7-hours-though-youd-need-to-look-closely-at-the-dashboard-to-know-it-happened/ https://thestack.technology/aws-us-east-1-wobbles-for-7-hour... (We have a policy here to never use us-east-1 - it's got to be the least reliable AWS region by quite a substantial margin.)