Bitbucket Pipelines fails on pulling our custom image from AWS ECR.
The error code from bitbucket pipelines: [rpc error: code = Unknown desc = failed to resolve image "xxx.dkr.ecr.ap-southeast-1.amazonaws.com/yyy:zzz": no available registry endpoint: unexpected status code https://xxxxx.dkr.ecr.ap-southeast-1.amazonaws.com/v2/yyy/manifests/zzz: 405 Method Not Allowed, rpc error: code = Unknown desc = failed to resolve image "xxx.dkr.ecr.ap-southeast-1.amazonaws.com/yyy:zzz": no available registry endpoint: unexpected status code https://xxx.dkr.ecr.ap-southeast-1.amazonaws.com/v2/yyy/manifests/zzz: 403 Forbidden]
We've had this pipeline running perfectly fine for the past few months, and now it stopped working.
I have tried using the exact same credentials in my docker cli and pull the image from ECR manually, and that worked fine, so the problem doesn't seem to be on the AWS side.
(I have replaced the repo and image names with xxx, yyy, and zzz for privacy reasons)
Hi @Tomas Svitil,
This issue likely corresponds with an incident that happened recently, if the issue persist I would suggest contacting our support at https://support.atlassian.com/contact/. If it works fine and re-occurs in the future keep an aye on the Bitbucket status page at https://bitbucket.status.atlassian.com/
...hey are a part of us, shaping how we interact with the world around us. The same holds true for programming languages when we think about how different kinds of vulnerabilities raise their heads in t...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events