Re:AWS us-east-1 outage
by jeremyjh on Tuesday December 07, 2021 @11:48AM
(#29474805)
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.
[ Parent
| 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.
Re:AWS us-east-1 outage
by packetslave on Tuesday December 07, 2021 @05:17PM
(#29478931)
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
Re:AWS us-east-1 outage
by bamboozled on Tuesday December 07, 2021 @08:04PM
(#29480213)
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 ?
Re:AWS us-east-1 outage
by silverlyra on Tuesday December 07, 2021 @04:41PM
(#29478574)
Same here. Kubernetes pods running in EKS are (intermittently) failing to get IAM credentials via the ServiceAccount integration.