from Hacker News

AWS Web Console Down?

by typicalrunt on 4/25/19, 4:30 PM with 49 comments

• by whatthesmack on 4/25/19, 4:43 PM

  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.

• by fiveoak on 4/25/19, 4:46 PM

  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

• by zedpm on 4/25/19, 4:40 PM

  FWIW, if you're already logged in to the console, it seems to be working just fine. In fact, if I try to go to a specific service page, e.g. https://s3.console.aws.amazon.com/s3/home?region=us-east-1# instead of just browsing to the console home page, that also appears to work.

• by DonHopkins on 4/25/19, 5:39 PM

  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 <ipalert@softlayer.com>)
          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: <201904251628.x3PGSB17029986@ipalert.theplanet.com>
      To: xxx@xxx.com
      From: <ipalert@softlayer.com>
      Subject: PROBLEM: xxx.xxx.com

• by kylek on 4/25/19, 4:55 PM

  I think the thing I miss most about AWS was sipping coffee while watching the #wtf peanut gallery on wednesday mornings and during events like this

• by rosencrantz on 4/25/19, 4:45 PM

  Looks like it is not reported having a look at the status dashboard https://status.aws.amazon.com/

• by mulka on 4/25/19, 4:46 PM

  Individual service pages seem to still be up. So, you can go to the EC2 page for example, click on the services dropdown on the top to select the service you want. https://console.aws.amazon.com/ec2/v2/home?region=us-east-1

• by busterarm on 4/25/19, 4:33 PM

  Can confirm that I am having this issue.

  API requests/CLI work fine though.

• by HatchedLake721 on 4/25/19, 4:38 PM

  You should be able to login through https://us-west-2.console.aws.amazon.com/console/home?region...

• by crystite on 4/25/19, 4:55 PM

  https://status.aws.amazon.com/

  Shows AWS Web Console:

  9:50 AM PDT We are investigating increased error rates when loading the AWS Management Console.

• by TheGRS on 4/25/19, 5:41 PM

  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.

• by crystite on 4/25/19, 5:01 PM

  According to the AWS Status Page

  Alternate link is available at: https://us-west-2.console.aws.amazon.com/ec2/v2/home

• by coffeesn0b on 4/25/19, 4:36 PM

  Is this the apocalypse?

• by zonywhoop on 4/25/19, 6:08 PM

  DynamoDB access via api in us-east-1 is down for me as well. Also, access to any region or resource through SSO is failing too.

• by goodfight on 4/25/19, 4:50 PM

  Strange, I'm experiencing this issue as well. Wonder if it's an attack or just normal failure

• by actionowl on 4/25/19, 4:40 PM

  Also having issues, the AWS status page is oblivious...

• by cortesoft on 4/25/19, 4:35 PM

  Same, came here to check if there was any info on it.

• by giffyUnicorn on 4/25/19, 4:54 PM

  confirmed, us-west works for logging into the console.

• by jshaw3 on 4/25/19, 4:40 PM

  us-east-1 is down for me

• by giffyUnicorn on 4/25/19, 4:50 PM

  well this is embarrassing.

• by hsk823 on 4/25/19, 4:43 PM

  So you can get to AWS resources going direct to the respective URLs, such as https://s3.console.aws.amazon.com/s3/ or https://console.aws.amazon.com/ec2/v2/ or even changing regions works. It seems to just affect https://console.aws.amazon.com/console/

• by tus87 on 4/25/19, 5:17 PM

  Everyone take the day off.