Live data from Hacker News

AWS Web Console Down?

news.ycombinator.com

41–50 of 55 posts

Re: AWS Web Console Down?

#41

It seems that the issue may be specific to us-east-1... https://console.aws.amazon.com/console/home?region=us-east-1 ...doesn’t work, but: https://us-west-2.console.aws.amazon.com/console/home?region... ...works.

[deleted]

Re: AWS Web Console Down?

#42
At least AWS doesn't start spamming you weeks after servers go down!

I canceled a dedicated server with IBM SoftLayer (nee ThePlanet), and a few weeks later I started receiving hourly IPAlerts about it being offline!

The server was canceled so there was nowhere in the interface for me to turn them off!

I opened a ticket, and they said other users were experiencing it too, and they though they had it fixed, and asked it I was still getting them. I was.

Their only suggestion was for me to make an email filter to ignore the IPAlerts, but what about the IPAlerts for servers I hadn't canceled that I actually want to see?

We went several rounds of this, each time they thought they had it fixed, and asked if I was still receiving them, and of course I was, like clockwork.

It's been more than a week and a half, and I'm STILL getting them!

I kept posting the raw email bodies so they could tell by the headers where it was coming from.

I even begged them to deploy one of their most powerful firewalls around the offending legacy nagios server to protect me from it, but they wouldn't do that.

I'm afraid if I cancel my other two servers and move to AWS, they's start spamming me with TWO MORE never-ending sets of IPAlerts about canceled servers!

What a passive-aggressive way of punishing long time customers for canceling their servers!

Has anybody experienced anything like this with AWS?

    Received:  from ipalert05.dllstx6.inside.theplanet.com
        by mx.softlayer.com with esmtps (TLSv1:DHE-RSA-AES256-SHA:256)
        (Exim)
        (envelope-from )
        for xxx@xxx.com
        id 1hJhFu-0003RG-Tm; Thu, 25 Apr 2019 11:29:50 -0500
    Received: (from nagios@localhost)
        by ipalert.theplanet.com (8.13.6/8.13.6/Submit) id x3PGSB17029986
        for xxx@xxx.com; Thu, 25 Apr 2019 11:28:11 -0500 (CDT)
        (envelope-from nagios)
    Date: Thu, 25 Apr 2019 11:28:11 -0500 (CDT)
    Message-Id: 
    To: xxx@xxx.com
    From: 
    Subject: PROBLEM: xxx.xxx.com

Re: AWS Web Console Down?

#43
I'll just report that we had an issue with an Elastic Beanstalk deployment that seems to have resolved itself now. Not sure if its related, but simply retrying the deployment resolved it without making any changes, so it sure seems related.

Re: AWS Web Console Down?

#44
post #15

It's annoying how often status pages for various services (when they even exist at all) show that things are working when they really aren't

If you can write a perfect automated status page - can't you basically write perfect integration tests and make sure no bad code gets deployed? Bit of a chicken and an egg problem :)

That may be true for small failures, but the AWS Status Page has routinely failed to report large scale outages.

Re: AWS Web Console Down?

#45

Earlier quoted context omitted.

If you can write a perfect automated status page - can't you basically write perfect integration tests and make sure no bad code gets deployed? Bit of a chicken and an egg problem :)

Do you write every single test for your codebase? Do you have control over every line of code that gets deployed? The purpose of monitoring is to detect issues, because preventing them entirely is next to impossible. By your logic if you can write perfect integration tests, can't you write perfect application code that doesn't need to be tested?

I think you've missed the point.

OP is arguing that a perfect codebase is not possible, therefore it's a bit unfair to complain that the status pages do not work perfectly. Hence the chicken and egg problem of "if I could write a perfect status page, I would have skills such that the status page would not be necessary".

Re: AWS Web Console Down?

#49

Earlier quoted context omitted.

I want status pages to show traffic to the status page itself over the last 24 hours (or some time period). A sudden uptick in traffic but green across the board would indicate that there is an issue, but they just haven't updated the page yet.

Yes! I have yet to convince anyplace I've been working to do this, but I do make increases in traffic volume to status pages generate non-critical alerts. Has caught out a few problems much earlier than they otherwise would have been discovered.

Sounds like an interesting way to make developers (or ops) life hell. Just point a traffic cannon at the status page and bingo bango non-critical page.
Post reply on HN