Bitbucket pipeline AWS ECR image name error

Question

I am trying to write a bitbucket-pipeline that uses the public AWS ECR image public.ecr.aws/sam/build-python3.9:1.58.0-20220929223133 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 ".dkr.ecr..amazonaws.com/" How can I reference this public image to avoid getting the Configuration error ? thanks

Theodora Boudale · Answer

Hi Sergey,

The variables with the credentials need to be removed only from the image definition. Instead of

image:
  name: public.ecr.aws/sam/build-python3.9:1.58.0-20220929223133
  aws: 
    access-key: $AWS_ACCESS_KEY
    secret-key: $AWS_SECRET_KEY

you need to use the following for public images

image:
  name: public.ecr.aws/sam/build-python3.9:1.58.0-20220929223133

or

image: public.ecr.aws/sam/build-python3.9:1.58.0-20220929223133

If you have added the variables $AWS_ACCESS_KEY and $AWS_SECRET_KEY as Repository, Workspace, or Deployment variables, you can still use them in the commands of the step's script in order to authenticate to AWS.

Kind regards,
Theodora

Sergey Akopov · Answer

@Theodora Boudale Removing credentials is not a solution in this case. The image is for AWS SAM which requires AWS credentials to execute commands against AWS.

Theodora Boudale · Answer

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 .dkr.ecr..amazonaws.com/ Please feel free to let me know if it works without the configuration for access and secret keys. Kind regards, Theodora