AWS us-east-1 down
1–10 of 331 posts
Re: AWS us-east-1 down
#2Re: AWS us-east-1 down
#3Re: AWS us-east-1 down
#4Contents:
> Has anyone ever actually had customers accept an outage because AWS was down; or is this just cloud evangelicalism copium?
> [ ] Yeah, outages free pass
> [ ] No, they say to use AZ's
Re: AWS us-east-1 down
#5Re: AWS us-east-1 down
#6Re: AWS us-east-1 down
#7Re: AWS us-east-1 down
#8def broken for us
Re: AWS us-east-1 down
#9Re: AWS us-east-1 down
#10I wonder if this is a coincidence or if us-east-1 is simply down enough that I'm just experiencing selection bias; but I posted a poll on twitter earlier today: https://twitter.com/dijit/status/1668678588713824257 Contents: > Has anyone ever actually had customers accept an outage because AWS was down; or is this just cloud evangelicalism copium? > [ ] Yeah, outages free pass > [ ] No, they say to use AZ's
Using 3 AZs in us-east-1 won't save you.
I guess a demanding customer would have said 'you should have implemented disaster recovery so you could failover to us-east-2' but that's easier said than done. The more regional AWS services you adopt, the bigger the impact is. How does one recover from a regional outage if their pipeline is in that region?