https://console.aws.amazon.com/console/home<p>It appears to be down, saying "Website temporarily unavailable". But it's intermittent for other employees at my company so it might be failing app services behind a load balancer.<p>CLI access or EC2 services doesn't appear to be affected, at least from us-east-1.<p>And, of course, the status health dashboard shows Green across the board. https://status.aws.amazon.com/<p><i></i><i>UPDATE</i><i></i><p>HatchedLake721 mentions that it appears to just be us-east-1 Web console that's down. Use this instead for now: https://us-west-2.console.aws.amazon.com/console/home?region=us-west-2<p>Thanks @HatchedLake721!
It seems that the issue may be specific to us-east-1...<p><a href="https://console.aws.amazon.com/console/home?region=us-east-1" rel="nofollow">https://console.aws.amazon.com/console/home?region=us-east-1</a><p>...doesn’t work, but:<p><a href="https://us-west-2.console.aws.amazon.com/console/home?region=us-west-2" rel="nofollow">https://us-west-2.console.aws.amazon.com/console/home?region...</a><p>...works.
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. <a href="https://s3.console.aws.amazon.com/s3/home?region=us-east-1#" rel="nofollow">https://s3.console.aws.amazon.com/s3/home?region=us-east-1#</a> instead of just browsing to the console home page, that also appears to work.
At least AWS doesn't start spamming you weeks after servers go down!<p>I canceled a dedicated server with IBM SoftLayer (nee ThePlanet), and a few weeks later I started receiving hourly IPAlerts about it being offline!<p>The server was canceled so there was nowhere in the interface for me to turn them off!<p>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.<p>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?<p>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.<p>It's been more than a week and a half, and I'm STILL getting them!<p>I kept posting the raw email bodies so they could tell by the headers where it was coming from.<p>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.<p>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!<p>What a passive-aggressive way of punishing long time customers for canceling their servers!<p>Has anybody experienced anything like this with AWS?<p><pre><code> 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</code></pre>
Looks like it is not reported having a look at the status dashboard <a href="https://status.aws.amazon.com/" rel="nofollow">https://status.aws.amazon.com/</a>
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. <a href="https://console.aws.amazon.com/ec2/v2/home?region=us-east-1" rel="nofollow">https://console.aws.amazon.com/ec2/v2/home?region=us-east-1</a>
You should be able to login through <a href="https://us-west-2.console.aws.amazon.com/console/home?region=us-west-2" rel="nofollow">https://us-west-2.console.aws.amazon.com/console/home?region...</a>
<a href="https://status.aws.amazon.com/" rel="nofollow">https://status.aws.amazon.com/</a><p>Shows AWS Web Console:<p>9:50 AM PDT We are investigating increased error rates when loading the AWS Management Console.
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.
According to the AWS Status Page<p>Alternate link is available at: <a href="https://us-west-2.console.aws.amazon.com/ec2/v2/home" rel="nofollow">https://us-west-2.console.aws.amazon.com/ec2/v2/home</a>
So you can get to AWS resources going direct to the respective URLs, such as <a href="https://s3.console.aws.amazon.com/s3/" rel="nofollow">https://s3.console.aws.amazon.com/s3/</a> or <a href="https://console.aws.amazon.com/ec2/v2/" rel="nofollow">https://console.aws.amazon.com/ec2/v2/</a> or even changing regions works. It seems to just affect <a href="https://console.aws.amazon.com/console/" rel="nofollow">https://console.aws.amazon.com/console/</a>