Re:4x Hour EC2 Outage for the Entire AWS Sydney Region
by wryun on Thursday January 23, 2020 @01:00AM
(#22125209)
The frustrating thing is this is also sending out other services (ECS Fargate, CodeBuild) that presumably can't allocate capacity, and they don't admit it on the status page (hey, it's still a 200!).
My favourite error of today:
{'ResponseMetadata': {'HTTPHeaders': {'content-length': '135',
'content-type': 'application/x-amz-json-1.1',
'date': 'Thu, 23 Jan 2020 04:16:02 GMT',
'x-amzn-requestid': '...'},
'HTTPStatusCode': 200,
'RequestId': '...',
'RetryAttempts': 0},
'failures': [{'reason': 'Capacity is unavailable at this time. Please try '
'again later or in a different availability zone'}],
'tasks': []}
My favourite error of today:
{'ResponseMetadata': {'HTTPHeaders': {'content-length': '135', 'content-type': 'application/x-amz-json-1.1', 'date': 'Thu, 23 Jan 2020 04:16:02 GMT', 'x-amzn-requestid': '...'}, 'HTTPStatusCode': 200, 'RequestId': '...', 'RetryAttempts': 0}, 'failures': [{'reason': 'Capacity is unavailable at this time. Please try ' 'again later or in a different availability zone'}], 'tasks': []}