3 Answers
- Newest
- Most votes
- Most comments
0
I am inexplicably experiencing this as well. Searching shows that this typically happens when AWS APIs are experiencing increased latencies.
I guess AWS doesn't know about it yet because it's not showing up in its status page.
Burnt an entire morning on this, how annoying they don't know about an issue like this and can't report status on it for hours after it started.
answered 3 years ago
0
The AWS status page now shows a RESOLVED event for this. Will try again.
answered 3 years ago
Relevant content
- asked 2 years ago
- asked 6 months ago
- asked 2 years ago
- Accepted Answerasked 4 years ago
- AWS OFFICIALUpdated 2 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 months ago
- How do I update a CloudFormation stack that's failing because of a resource that I manually deleted?AWS OFFICIALUpdated 3 years ago