6 ms·
AWS Web Console Down?
https://console.aws.amazon.com/console/home
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!
- giffyUnicorn 7y agoconfirmed, us-west works for logging into the console.
- busterarm 7y agoCan confirm that I am having this issue. API requests/CLI work fine though.
- cortesoft 7y agoSame, came here to check if there was any info on it.
- hsk823 7y agoSame here, website temporarily unavailble
- coffeesn0b 7y agoIs this the apocalypse?
- HatchedLake721 7y agoYou should be able to login through https://us-west-2.console.aws.amazon.com/console/home?region=us-west-2 https://us-west-2.console.aws.amazon.com/console/home?region...
- bdcravens 7y agoAnd then switch to us-east-1 services?
- nyczomg 7y agoI can get redirected to a login page if I go directly to an aws service like: https://console.aws.amazon.com/rds/ https://console.aws.amazon.com/rds/
- jshaw3 7y agous-east-1 is down for me
- zedpm 7y agoFWIW, 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# 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.
- PDFormat 7y agoThis way worked for me too. I was able to go straight to the Lambda console.
- actionowl 7y agoAlso having issues, the AWS status page is oblivious...
- whatthesmack 7y agoIt seems that the issue may be specific to us-east-1... https://console.aws.amazon.com/console/home?region=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=us-west-2 https://us-west-2.console.aws.amazon.com/console/home?region... ...works.
- codecrane 7y agoBoth of those are working for me. Much appreciated!
- deleted 7y ago[deleted]
- hsk823 7y agoSo you can get to AWS resources going direct to the respective URLs, such as https://s3.console.aws.amazon.com/s3/ https://s3.console.aws.amazon.com/s3/ or https://console.aws.amazon.com/ec2/v2/ https://console.aws.amazon.com/ec2/v2/ or even changing regions works. It seems to just affect https://console.aws.amazon.com/console/ https://console.aws.amazon.com/console/
- rosencrantz 7y agoLooks like it is not reported having a look at the status dashboard https://status.aws.amazon.com/ https://status.aws.amazon.com/
- sgt 7y agoThey follow the industry standard of hard coding their status dashboards.
- fiveoak 7y agoIt'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
- loudtieblahblah 7y agoIt's bc they're manually updated.
- skrebbel 7y agoI've always wondered about this strategy. I'm a developer and a business owner. I'm in AWS's core target demographic. I know three things about AWS: - Their products have weird names - Their web console has horrible UX - The lie about uptime and server status I'm not looking to switch to AWS soon.
- philg_jr 7y agoI take it you have never used Azure's UI? AWS is much better. I can't comment on Google Cloud because I've never used it.
- KZeillmann 7y agoSome of the AWS UX is okay but the parameter store UX for the web console is some of the worst I've seen. It's difficult to navigate and paginate, and the search function is barely worth using. It would be amazing if they had fuzzy search on the names.
- philg_jr 7y agoI do agree that the CloudWatch console search is like this, where you need to type out the entire string from the beginning to get it to match. But for the CloudFormation and Lambda consoles, I can just type a piece of the string I'm trying to find and all matching will just show up.
- gtsteve 7y ago
- mulka 7y agoIndividual 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 https://console.aws.amazon.com/ec2/v2/home?region=us-east-1
- giffyUnicorn 7y agowell this is embarrassing.
- goodfight 7y agoStrange, I'm experiencing this issue as well. Wonder if it's an attack or just normal failure
- kylek 7y agoI 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
- an_account_name 7y ago!fq cockroaches
- amazon_throw 7y agoIn the post-nuclear-holocaust wasteland where only cockroaches survive, the cockroaches will use IRC to rebuild.
- crystite 7y agohttps://status.aws.amazon.com/ 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.
- crystite 7y agoAWS keeps their status page up2date these days. It's probably easier to check that page than combing through posts on HN, but to each their own. 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?
- nerdjon 7y agoThe status page was stating all green for about 20 or so minutes after this post was made. Not really "up2date", so this post was valuable for everyone that was seeing errors and unsure how widespread it was.
- ulysses 7y agoThe date on the status page is 9:50 AM PDT, the original poster posted well before that. It isn't historically uncommon for AWS outage information to be posted and commented on here well before the status page is updated.
- deleted 7y ago[deleted]
- crystite 7y agoAccording to the AWS Status Page Alternate link is available at: https://us-west-2.console.aws.amazon.com/ec2/v2/home https://us-west-2.console.aws.amazon.com/ec2/v2/home
- tus87 7y agoEveryone take the day off.
- deleted 7y ago[deleted]
- DonHopkins 7y agoAt 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
- TheGRS 7y agoI'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.
- zonywhoop 7y agoDynamoDB 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.
- slenk 7y agoI am having issues with SAML authentication as well