![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
So you have your infrastructure in AWS, and you store docker images in AWS ECR.
But your customer has own AWS account, and you need to copy new versions of images to his ECR on a regular manner.
Or you need to promote images between environments, each in an own isolated AWS account. You know, common approach Dev -> Test -> Preprod -> Prod, or whatever you have in your infrastructure.
Now it is easier with my aws-ecr-cross-account-clone tool.
In fact, it automates docker pull-tag-push sequence on a host-in-the-middle, adding a couple of rules on what to copy and what not to copy. By now, two filters are supported - by image age and by scan completion status.
GPL-2.0, feel free to use.
But your customer has own AWS account, and you need to copy new versions of images to his ECR on a regular manner.
Or you need to promote images between environments, each in an own isolated AWS account. You know, common approach Dev -> Test -> Preprod -> Prod, or whatever you have in your infrastructure.
Now it is easier with my aws-ecr-cross-account-clone tool.
In fact, it automates docker pull-tag-push sequence on a host-in-the-middle, adding a couple of rules on what to copy and what not to copy. By now, two filters are supported - by image age and by scan completion status.
GPL-2.0, feel free to use.
