Harbor Replication Issue with ECR in another AWS account #21828
Labels
help wanted
The issues that is valid but needs help from community
replication/adapters
related to replication adapters
Harbor is running in an EKS cluster with a service account that has an IAM role, in AWS account
11111111
.Harbor is configured to replicate images to an ECR repository in AWS account
22222222
. The IAM role for Harbor has been granted access to the ECR in account22222222
. Additionally, Harbor has access to the ECR in the same AWS account (11111111
) where it is running.Expected Behavior:
Harbor should create a repository and upload an image directly to the target ECR in AWS account
22222222
.Actual Behavior:
Harbor creates a repository in AWS account
11111111
and uploads the image to the ECR in AWS account22222222
only if the repository already exists.Steps to Reproduce:
11111111
.22222222
to Harbor.22222222
.Versions:
Please specify the versions of following systems.
Additional Information:
Failed to do the prepare work for pushing/uploading resources: AccessDeniedException: User: arn:aws:sts::11111111:assumed-role/eks-eu-west-1-harbor/eks-... is not authorized to perform: ecr:DescribeRepositories on resource: arn:aws:ecr:eu-west-1:11111111:repository/container-registry/app because no identity-based policy allows the ecr:DescribeRepositories action status code: 400, request id: 7a6a..
event_based
The text was updated successfully, but these errors were encountered: