Hacker News Reader

Comment by jeremyjh | Hacker News Reader

They are still lying about it, the issues are not only affecting the console but also AWS operations such as S3 puts. S3 still shows green.

View on HN

It's certainly affecting a wider range of stuff from what I've seen. I'm personally having issues with API Gateway, CloudFormation, S3, and SQS

Our corporate ForgeRock 2FA service is apparently broken. My services are behind distributed x509 certs so no problems there.

> We are experiencing API and console issues in the US-EAST-1 Region

I read it as console APIs. Each service API has its own indicator, and they are all green.

IAM is a "global" service for AWS, where "global" means "it lives in us-east-1".

STS at least has recently started supporting regional endpoints, but most things involving users, groups, roles, and authentication are completely dependent on us-east-1.

Yep, I am seeing failures on IAM as well:

   aws iam list-policies
  
  An error occurred (503) when calling the ListPolicies operation (reached max retries: 2): Service Unavailable

I'm seeing errors for things that worked fine, like policies that had no issue now are saying "access denied".

I'm wondering if the cause of the outage has to do with something changing in the way IAM is interpreted ?

Same here. Kubernetes pods running in EKS are (intermittently) failing to get IAM credentials via the ServiceAccount integration.

I still can't create/destroy/etc CloudFront distros. They are stuck in "pending" indefinitely.

Reply on news.ycombinator.com