Friends tell friends to pick us-east-2. Virginia is for lovers, Ohio is for availability.
If you're not multi-cloud in 2021 and are expecting 5-9's, I feel bad for you.
AWS us-east-1 outage
131–140 of 1001 posts
Re: AWS us-east-1 outage
#132Friends tell friends to pick us-east-2. Virginia is for lovers, Ohio is for availability.
Ohio's actual motto funnily kind of fits here:
With God, all things are possibleRe: AWS us-east-1 outage
#133Earlier quoted context omitted.
Is this true or a joke? This sort of policy is how you destroy trust.
From what I've heard it's mostly true. Not only the CEO but a few SVPs can approve it, but yes a human must approve the update and it must be a high level exec. Part of the reason is because their SLAs are based on that dashboard, and that dashboard going red has a financial cost to AWS, so like any financial cost, it needs approval.
I wonder how well known this is. You'd think it would be hard to hire ethical engineers with such a scheme in place and yet they have tens of thousands.
Re: AWS us-east-1 outage
#134Re: AWS us-east-1 outage
#135I'm going with "BGP error" which is likely config-related, likely human error.
Seems to be the trend with the last 5-6 big cloud outages.
Re: AWS us-east-1 outage
#136"AWS Management Console Home page is currently unavailable. You can monitor status on the AWS Service Health Dashboard."
And then Health Dashboard is 100% green. What a joke.
Re: AWS us-east-1 outage
#137Earlier quoted context omitted.
From what I've heard it's mostly true. Not only the CEO but a few SVPs can approve it, but yes a human must approve the update and it must be a high level exec. Part of the reason is because their SLAs are based on that dashboard, and that dashboard going red has a financial cost to AWS, so like any financial cost, it needs approval.
Being dishonest about SLAs seems to bear zero cost in this case?
It's not really dishonest though because there is nuance. Most everything in EC2 is still working it seems, just the console is down. So is it really down? It should probably be yellow but not red.
Re: AWS us-east-1 outage
#138I love that every time this happens, 100% of the services on https://status.aws.amazon.com are green.
The problem being that often times you can't actually update the status page. Most internal systems are down.
We can't even update our product to say it's down, because accessing the product requires a process that is currently dead.
Re: AWS us-east-1 outage
#139We're not down and we're in us-east-1... maybe there is more to this issue?
Everything fine with S3 in us-east-1 for me. Also just not able to access the console.
Re: AWS us-east-1 outage
#140No wonder I could not read books from amazon all of a sudden, what about their cloud-based redundancy design?
The book preview webservice or actual ebooks (kindle, etc)?