4 ms·

The thing AWS does which can be described as amateur, was the communication. AWS has always been really quiet when there's an issue on their services. It's a n

The thing AWS does which can be described as amateur, was the communication. AWS has always been really quiet when there's an issue on their services. It's a nightmare to know when your problem is due to your infrastructure or if their's a bigger scale issue at AWS cause they never talk about it...

mkr-hn 13y ago
Amazon has a status page for all AWS services and provides RSS feeds for each: http://status.aws.amazon.com/ http://status.aws.amazon.com/
- sebgeelen 13y ago
  I know. Sadly this page is not updated often enough. I mean, when there's a known issue on one of the aws service this page display a little "i" icon, which is barely visible. And when, you encounter some problem with your AWS stuff that clearly come from their side, if the problem it's not wide, they just say nothing. At that point you can search yourself for hour to be sure it's not your responsibility, and after-woods, you just wait, blind.
- deleted 13y ago
  [deleted]
- madaxe_again 13y ago
  Trust me, this doesn't cover all their issues. Don't get me wrong, we love our AWS stack, but we've had all sorts of weird stuff happen over the years, from zombie ELBs hitting the wrong hosts to invisible SGs... sometimes we see from twitter that others are seeing the same things, but AWS don't ever confirm or deny anything, they just stall then tell you when it's fixed. I guess its support in terms of something to give to your PHB, but when something goes wrong within AWS, it's a very black box - which isn't surprising.
madaxe_again 13y ago
They're not amateur. We pay for their premium support and their communication is professional, polite, and usually totally useless.
- mrjatx 13y ago
  Their communication is not impressive. I work with AWS daily and I've been aware of issues LONG before they publicly announce anything on their status pages.
brown9-2 13y ago
Typically AWS is great at communicating with post-mortems, for example: http://aws.amazon.com/message/2329B7/ http://aws.amazon.com/message/2329B7/ In this case, they probably didn't want to be too explicit about the details of patching tens of thousands of machines while the remediation was still ongoing. I do agree that it's unexpectedly hard to find a link to the "security notice" page anywhere.
- westernmostcoy 13y ago
  That outage notice you've linked includes a promise to improve communication. Also, how'd you find that link? If you happened to just have it laying around, that's fine but it would be better if they had these things linked somewhere customers can find them when new ones are posted (like a page covering service post-mortems) and the timeline is missing little details like the year when the outage happened and a point of contact (it's signed by "the aws team") if you have questions.
  - brown9-2 13y ago
    it would be better if they had these things linked somewhere customers can find them when new ones are posted That's a great point. I found it by googling "AWS post mortem", but I only knew it existed because I had been linked to this page before.

mkr-hn 13y ago

Amazon has a status page for all AWS services and provides RSS feeds for each: http://status.aws.amazon.com/ http://status.aws.amazon.com/

sebgeelen 13y ago
I know. Sadly this page is not updated often enough. I mean, when there's a known issue on one of the aws service this page display a little "i" icon, which is barely visible. And when, you encounter some problem with your AWS stuff that clearly come from their side, if the problem it's not wide, they just say nothing. At that point you can search yourself for hour to be sure it's not your responsibility, and after-woods, you just wait, blind.
deleted 13y ago
[deleted]
madaxe_again 13y ago
Trust me, this doesn't cover all their issues. Don't get me wrong, we love our AWS stack, but we've had all sorts of weird stuff happen over the years, from zombie ELBs hitting the wrong hosts to invisible SGs... sometimes we see from twitter that others are seeing the same things, but AWS don't ever confirm or deny anything, they just stall then tell you when it's fixed. I guess its support in terms of something to give to your PHB, but when something goes wrong within AWS, it's a very black box - which isn't surprising.

madaxe_again 13y ago

They're not amateur. We pay for their premium support and their communication is professional, polite, and usually totally useless.

mrjatx 13y ago
Their communication is not impressive. I work with AWS daily and I've been aware of issues LONG before they publicly announce anything on their status pages.

brown9-2 13y ago

Typically AWS is great at communicating with post-mortems, for example: http://aws.amazon.com/message/2329B7/ http://aws.amazon.com/message/2329B7/ In this case, they probably didn't want to be too explicit about the details of patching tens of thousands of machines while the remediation was still ongoing. I do agree that it's unexpectedly hard to find a link to the "security notice" page anywhere.

westernmostcoy 13y ago
That outage notice you've linked includes a promise to improve communication. Also, how'd you find that link? If you happened to just have it laying around, that's fine but it would be better if they had these things linked somewhere customers can find them when new ones are posted (like a page covering service post-mortems) and the timeline is missing little details like the year when the outage happened and a point of contact (it's signed by "the aws team") if you have questions.
- brown9-2 13y ago
  it would be better if they had these things linked somewhere customers can find them when new ones are posted That's a great point. I found it by googling "AWS post mortem", but I only knew it existed because I had been linked to this page before.