3 ms·
AWS itself has a huge single point of failure on us-east-1 region. Usually, if us-east-1 goes down, others soon follow. At that point, it doesn't matter how man
by simmanian 5y ago
AWS itself has a huge single point of failure on us-east-1 region. Usually, if us-east-1 goes down, others soon follow. At that point, it doesn't matter how many regions you're deploying to.
- scoopertrooper 5y agoMy workloads on Sydney and London are unaffected. I can't speak for anywhere else.
- lowbloodsugar 5y ago"Usually"? When has that ever happened?
- dylan604 5y agohttps://awsmaniac.com/aws-outages/ https://awsmaniac.com/aws-outages/
- lowbloodsugar 5y agoThanks. That shows that OPs claim that "Usually, if us-east-1 goes down, others soon follow." is false.
- dijit 5y agoCognito (and r53) have hard dependencies in us-east-1. It’s mentioned up and down this thread.
- lowbloodsugar 5y agoI don't want to minimize the impact from cognito and r53, but that's quite a different scale of failure than the OP implies. It's been a while since I used AWS, but we had multiple regions and saw no impact to our services in other regions the one time that us-east-1 had a major failure. And we used r53.
- simmanian 5y agoPerhaps I could've been more precise with my words. What I meant to say is IAM and r53 are two of many critical services that all depend on us-east-1. It goes without saying that if those services go down in us-east-1, the whole AWS is affected. This doesn't just happen "usually." When IAM goes down, AWS experiences major issues across all regions. If you were okay, perhaps you got lucky? Our team has 7 different prod regions and we see multiple regions go down every time a problem of this scale occurs. If your product requires 100% uptime, you may need to look at backup options or design your product in such a way that can handle temporary cloud failures.