2 Answers
- Newest
- Most votes
- Most comments
1
I was facing the same error.
In my case, my problem was that the af-south-1 region was not enabled in the aws account where my principal was configured.
in summary, if you have the principal:
"Principal":{
"AWS":"arn:aws:iam::1111111111111:root"
}
then you must enable af-sout-1 region in the 1111111111111
account to be able to configure the policy.
answered 8 months ago
-1
Try this permission { "Version": "2012-10-17", "Statement": [ { "Effect": "Allow", "Action": [ "ecr:GetAuthorizationToken", "ecr:BatchCheckLayerAvailability", "ecr:GetDownloadUrlForLayer", "ecr:GetRepositoryPolicy", "ecr:DescribeRepositories", "ecr:ListImages", "ecr:DescribeImages", "ecr:BatchGetImage", "ecr:GetLifecyclePolicy", "ecr:GetLifecyclePolicyPreview", "ecr:ListTagsForResource", "ecr:DescribeImageScanFindings" ], "Resource": "*" } ] }
answered 9 months ago
Relevant content
- Accepted Answerasked a year ago
- asked a year ago
- asked 3 months ago
- Accepted Answerasked 5 months ago
- AWS OFFICIALUpdated 8 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
Thank you for this, this was exactly what it was. The error is very misleading, but as mentioned af-south-1 isn't on by default ( will apply to any region that is optional )