4 ms·
Ask HN: Is AWS SSM (or other services) down for anyone else?
We're experiencing production issues due to SSM in us-east-1.
- kennu 4y agoAmazon Web Services Service Status 18:46 Informational message: Increased API Error Rates and Latency We are investigating increased API error rates and latency in the US-EAST-1 Region. This will impact customers ability to make calls to parameter store. (from RSS feed, time is EET)
- kennu 4y agoI can't deploy on CloudFormation to us-east-1 right now, getting various errors when creating changesets with AWS CDK.
- ack210 4y agoYes, also in us-east-1 and we currently have an event showing for it in our personal health dashboard (but doesn't seem to be acknowledged on the health dashboard if logged out). It's preventing us from deploying CloudFormation stacks as well right now. https://imgur.com/a/4fMho2O https://imgur.com/a/4fMho2O
- juleska 4y agoSame here, seems to be recovering ...
- JimTheDev 4y agoAWS saying it will be an hour until resolution.
- JimTheDev 4y agoThey just pulled that back. Resolution time is now unknown.
- colpabar 4y agoYep. I have seen these errors botocore.errorfactory.InternalServerError: An error occurred (InternalServerError) when calling the GetParameter operation (reached max retries: 4): Server busy. Please try again. botocore.errorfactory.InternalServerError: An error occurred (InternalServerError) when calling the GetParameter operation (reached max retries: 4): No Content-Type received. Service returned the HTTP status code: 500
- Lapalux 4y agoGetting CloudFront internal errors preventing deployment... `An error occurred (ServiceUnavailable) when calling the CreateInvalidation operation (reached max retries: 2): CloudFront encountered an internal error. Please try again.`
- adeeshaek 4y agoUs too - ssm is returning `software.amazon.awssdk.services.ssm.model.InternalServerErrorException: Server busy. Please try again. `
- Scottsa 4y ago[flagged]