Yep, PHD isn't loading, Cloudwatch is reporting SQS errors, metrics aren't loading, can't pull logs. This is in US-East-1.
AWS us-east-1 outage
11–20 of 1001 posts
Re: AWS us-east-1 outage
#12It seems that only console is having the problem CLI works fine
Re: AWS us-east-1 outage
#13I love that every time this happens, 100% of the services on https://status.aws.amazon.com are green.
Re: AWS us-east-1 outage
#14[deleted]
Re: AWS us-east-1 outage
#15EKS works for us
Re: AWS us-east-1 outage
#16I think the only the console is down. CLI is working fine for me in ap-southeast-1
Re: AWS us-east-1 outage
#17It seems that only console is having the problem CLI works fine
Not entirely true- we federate through ADFS and `saml2aws login` is currently failing with:
error logging into aws role using saml assertion: error retrieving STS credentials using SAML: ServiceUnavailable: status code: 503
Re: AWS us-east-1 outage
#18It's funny that the first place I go to learn about the outage is Hacker News and not https://status.aws.amazon.com/ (it's still reports everything to be "operating normally"...)
Re: AWS us-east-1 outage
#19It seems that only console is having the problem CLI works fine
I'm having CLI issues as well, they're using the same APIs under the hood. For example, I'm getting 503 errors for cloudwatch DescribeLogGroups.
Re: AWS us-east-1 outage
#20I love that every time this happens, 100% of the services on https://status.aws.amazon.com are green.
On top of that, the "Personalized Health Dashboard" doesn't work because I can't seem to log in to the console.