AWS ECR Push Image Specify Registry ID

[Dave McDermid]

With the aws-ecr-push-image pipe it would be really useful to be able to pass the Registry ID (AWS Account ID) as a parameter. This is required when the user belongs to a different AWS account than the registry it is pushing to.

Thanks

[Alexander Zhukov · Accepted solution]

Hi @Dave McDermid , thank you for your suggestion, will consider adding this feature to the pipe.

[Dave McDermid]

Great, thanks.

[siddharthjoshi]

@Dave McDermid Has this been implemented yet ? 

Would a registry id be needed to even push to a public registry within the same account, in my case I am getting the following error and during build the repository is being searched under private only and not public

"The repository with name 'xxxxxxxx' does not exist in the registry with id 'xxxxxxxxx'"

[Anton Patronov]

@Alexander Zhukovdo you have a ticket we this feature request?

[Einar Coutin]

This hasn't been implemented yet, either implement this or please add support for AWS STS Assume Role rather than go overboard with OIDC. Some of us have our runners in AWS and would like to keep them separate from the devs while still giving them visibility into the registry for things like container image scan results. 
Either an STS assume role of specifying the account ID rather than access keys or simply specifying the AWS account Id and combining that with a Resource Policy on the ECR repo itself.

[Einar Coutin]

@Dave McDermid @Anton Patronov @Alexander Zhukov 
I created a discussion for this issue here:
Feature request - aws-ecr-push-image - add simpler... (atlassian.com)