Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


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

Bitbucket pipeline AWS ECR image name error


I am trying to write a bitbucket-pipeline that uses the public AWS ECR image
but I am getting the error:

Configuration error

Invalid AWS Elastic Container Registry image name at [pipelines > custom > build-test-lambda-python-layer > 2 > step > image > name]. Expecting "<accountId>.dkr.ecr.<region><image-name>"


How can I reference this public image to avoid getting the Configuration error ? thanks


Screen Shot 2022-09-30 at 20.37.26.png

1 answer

0 votes
Theodora Boudale
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Oct 03, 2022

Hi @Nehemias Herrera,

I have no issues using this image as a build container in a Pipelines build with a configuration as follows:

- step:
- echo "hello"

Do you have additional details in your configuration? E.g. are you providing an access key and secret key?

Kind regards,

Theodora, thanks for you reply,

Yes, we are providing our access and secrets keys but those are not needed since is a public registry and does not require credentials (.i.e. just try running docker pull to verify this image can be downloaded without logging in to the registry.


Nehemias ✌️

I see, maybe the credentials are the problem, will try getting rid of them and let you know

Theodora Boudale
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Oct 04, 2022

Hi Nehemias,

Yes, I think that's what's causing the issue; since you provide an access key and secret key, the yml file expects a private aws image with a name in the form of <accountId>.dkr.ecr.<region><image-name>

Please feel free to let me know if it works without the configuration for access and secret keys.

Kind regards,

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events