Some sage advice I learned a while ago: "Avoid us-east-1 as much as possible".
AWS us-east-1 outage
591–600 of 1001 posts
Re: AWS us-east-1 outage
#592Re: AWS us-east-1 outage
#593Earlier quoted context omitted.
You and many others here may be conflating two concepts which are actually quite separate. Taking blame is a purely punitive action and solves nothing. Taking responsibility means it's your job to correct the problem. I find that the more "political" the culture in the organization is, the more likely everyone is to search for a scapegoat to protect their own image when a mistake happens. The higher you go up in the…
Every argument I have on the internet is between prescriptive and descriptive language. People tend to believe that if you can describe a problem that means you can prescribe a solution. Often times, the only way to survive is to make it clear that the first thing you are doing is describing the problem. After you do that, and it's clear that's all you are doing, then you follow up with a prescriptive description whe…
Re: AWS us-east-1 outage
#594"some customers may experience a slight elevation in error rates" --> everything is on fire
Re: AWS us-east-1 outage
#595Re: AWS us-east-1 outage
#596Earlier quoted context omitted.
Ok, and? I don't doubt it fails in places. That doesn't mean that it doesn't work in practice. Our company does it just fine. We have a high trust, high transparency system and it's wonderful. It's like saying unit tests don't work in practice because bugs got through.
Have you ever considered that the “no-blame” postmortems you are giving credit for everything are just a side effect of living in a high trust, high transparency system? In other words, “no-blame” should be an emergent property of a culture of trust. It’s not something you can prescribe.
Re: AWS us-east-1 outage
#597Earlier quoted context omitted.
Yeah, strange, my self-hosted server isn't affected either.
Seems "the cloud" had a major outage less than a month ago, my laptop has a higher uptime. $ 16:04 up 46 days, 7:02, 9 users, load averages: 3.68 3.56 3.18 US East 1 was down just over a year ago https://www.theregister.com/2020/11/25/aws_down/ Meanwhile I moved one of my two internal DNS servers to a second site on 11 Nov 2020, and it's been up since then. One of my monitoring machines has been filling, rotating and…
Re: AWS us-east-1 outage
#598Earlier quoted context omitted.
I worked at Walmart Technology. I bravely wrote post mortem documents owning the fault of my team (100+ people), owning both technically and also culturally as their leader. I put together a plan to fix it and executed it. Thought that was the right thing to do. This happend two times in my 10 year career there. Both times I was called out as a failure in my performance eval. Second time, I resigned and told them to…
That's shockingly stupid. I also worked for a major Walmart IT services vendor in another life, and we always had to be careful about how we handled them, because they didn't always show a lot of respect for vendors. On another note, thanks for building some awesome stuff -- walmart.com is awesome. I have both Prime and whatever-they're-currently-calling Walmart's version and I love that Walmart doesn't appear to mix…
Re: AWS us-east-1 outage
#599Earlier quoted context omitted.
They are still lying about it, the issues are not only affecting the console but also AWS operations such as S3 puts. S3 still shows green.
It's certainly affecting a wider range of stuff from what I've seen. I'm personally having issues with API Gateway, CloudFormation, S3, and SQS
Re: AWS us-east-1 outage
#600Amazon is having an outage in us-east-1, and it is bleeding over elsewhere, like eu: https://status.aws.amazon.com/