Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

How can I access pipes that are deployed in AWS ECR


We're using AWS ECR to store our private images.  We've figured out how to access our images in a BB pipeline, however, I haven't figured out how to access a pipe in ECR yet.  

When I execute my pipeline, I get an error about being unable to find the pipe:

- step:
name: "Checkout and deploy our update"
- pipe:


Configuration error

It looks like you tried to use a pipe in your bitbucket-pipelines.yml that doesn’t exist. Check the name of the pipe and try again.


In order to solve our issue with private docker images on the build we added some AWS credential configuration:

from bitbucket-pipelines.yml:

access-key: $AWS_ACCESS_KEY_ID

Is there a similar configuration on the pipe element that we can use to access our pipe image in ECR? 

1 answer

1 accepted

1 vote
Answer accepted
Raul Gomis Atlassian Team May 23, 2019

Hey @brianrook ,

If you are referencing the docker image directly you will need to use docker://:

- step:
name: "Checkout and deploy our update"
- pipe: docker://

Bear in mind that we only support public docker images for now. If you need support for private images you can vote and comment with your use case here: so that we can gauge the interest on it.



Can we make this more explicit in the documentation?


Just to be clear, I know that it shows the docker:// prefix in  the documentation. It doesn't specify that it must be there for ALL public docker images; not just ones on Dockerhub.

I had an image public on GCP artifact registry and was trying things like gcp://...doh!!

Like Raul Gomis likes this

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Bitbucket

Git push size limits are coming to Bitbucket Cloud starting April 4th, 2022

Beginning on April 4th, we will be implementing push limits. This means that your push cannot be completed if it is over 3.5 GB. If you do attempt to complete a push that is over 3.5 GB, it will fail...

2,229 views 2 9
Read article

Community Events

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

Events near you