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.
CLI access or EC2 services doesn't appear to be affected, at least from us-east-1.
And, of course, the status health dashboard shows Green across the board. https://status.aws.amazon.com/
UPDATE
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
Thanks @HatchedLake721!
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.
Bit of a chicken and an egg problem :)
By your logic if you can write perfect integration tests, can't you write perfect application code that doesn't need to be tested?
- Their products have weird names
- Their web console has horrible UX
- The lie about uptime and server status
I use the AWS APIs almost every day but probably log in once a week or so.
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.comAPI requests/CLI work fine though.
Shows AWS Web Console:
9:50 AM PDT We are investigating increased error rates when loading the AWS Management Console.
This makes me wonder... do people keep posting and looking here because they want an element of control, they don't trust or know about status.aws.amazon.com ... or why?
Not really "up2date", so this post was valuable for everyone that was seeing errors and unsure how widespread it was.
It isn't historically uncommon for AWS outage information to be posted and commented on here well before the status page is updated.
Alternate link is available at: https://us-west-2.console.aws.amazon.com/ec2/v2/home