4 ms·
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.
by jeremyjh 5y ago
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.
- lsaferite 5y agoIt'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
- pbalau 5y ago> We are experiencing API and console issues in the US-EAST-1 Region
- jeremyjh 5y agoI read it as console APIs. Each service API has its own indicator, and they are all green.
- midasuni 5y agoOur corporate ForgeRock 2FA service is apparently broken. My services are behind distributed x509 certs so no problems there.
- Rantenki 5y agoYep, 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
- silverlyra 5y agoSame here. Kubernetes pods running in EKS are (intermittently) failing to get IAM credentials via the ServiceAccount integration.
- bamboozled 5y agoI'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 ?
- packetslave 5y agoIAM 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.
- Rapzid 5y agoI still can't create/destroy/etc CloudFront distros. They are stuck in "pending" indefinitely.