Our Bitbucket pipeline didn't have any changes and now started to fail for some reason with:
ontent-type:application/x-amz-json-1.1
host:ecs.us-east-1.amazonaws.com
x-amz-date:20210817T154801Z
x-amz-target:AmazonEC2ContainerServiceV20141113.UpdateService
content-type;host;x-amz-date;x-amz-target
3850981412382e2c1ae4cd3325ded13c1006413ac6eda6cab047a39db44a2d85
DEBUG: StringToSign:
AWS4-HMAC-SHA256
20210817T154801Z
20210817/us-east-1/ecs/aws4_request
05b2ff041099d36abbf116367d5f17808ba28d046d0e31188ece3e77868154c3
DEBUG
: Sending http request: <AWSPreparedRequest stream_output=False, method=POST, url=https://ecs.us-east-1.amazonaws.com/, headers={'X-Amz-Target': b'AmazonEC2ContainerServiceV20141113.UpdateService', 'Content-Type': b'application/x-amz-json-1.1', 'User-Agent': b'Boto3/1.9.139 Python/3.7.4 Linux/5.4.92-flatcar Botocore/1.12.187', 'X-Amz-Date': b'20210817T154801Z', 'Authorization': b'AWS4-HMAC-SHA256 Credential=AKIAZIZFNPKKL4HVQT55/20210817/us-east-1/ecs/aws4_request, SignedHeaders=content-type;host;x-amz-date;x-amz-target, Signature=4142a6faf487347b4568c2db1fb1f9cde43c425fa4a1c88ef43ce0631b6455ab', 'Content-Length': '160'}>
DEBUG: Converted retries value: False -> Retry(total=False, connect=None, read=None, redirect=0, status=None)
DEBUG: Starting new HTTPS connection (1): ecs.us-east-1.amazonaws.com
DEBUG: https://ecs.us-east-1.amazonaws.com:443 "POST / HTTP/1.1" 400 37
DEBUG: Response headers: {'x-amzn-RequestId': 'aba9ae17-13e1-42b6-8265-94d14ccc4bc9', 'Content-Type': 'application/x-amz-json-1.1', 'Content-Length': '37', 'Date': 'Tue, 17 Aug 2021 15:48:02 GMT', 'Connection': 'close'}
DEBUG: Response body:
b'{"__type":"ClusterNotFoundException"}'
DEBUG: Event needs-retry.ecs.UpdateService: calling handler <botocore.retryhandler.RetryHandler object at 0x7f968020ad50>
DEBUG: No retry needed.
✖ ECS cluster not found. Check your ECS_CLUSTER_NAME.
Does anyone know, if some outage is happening on Bitbucket side or AWS side? Or some configuration changed? My current pipeline was working and deploying to ECS all this 1 year already and no changes actually were added to repo,
Best Regards,
Vitali
@vitali you did not change the pipeline, but , perhaps, did change the setup in your cloud.
It says: ClusterNotFoundException
, that means that someone with access to your aws deleted specific cluster that you want to update.
Regards, Galyna
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.