- Newest
- Most votes
- Most comments
Have you tried this before build and push?
aws ecr get-login-password --region ${REGION} | docker login --username AWS --password-stdin ${AWS_ACCOUNT_ID}.dkr.ecr.${REGION}.amazonaws.com
Yes, I followed all the instructions as per the following documentation: https://docs.aws.amazon.com/AmazonECR/latest/userguide/docker-push-ecr-image.html
I figure that more contextual debugging might be required for my situation. I would appreciate any ways to debug and find out what is causing the issue.
Is the repository public or private since the policy you have quoted above is for a public repository. If you have private repository, the policies should be ecr:xxx and not ecr-public:xxx
Thanks so much for the responses!
When I changed the region for the ECR and pushed the image, it worked! I am not sure why a region would make a difference.
Now I have my Image->ECR->ECS->Cluster up and running. Thanks!
Relevant content
- asked 6 months ago
- asked a year ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 10 months ago
These are my 'Actions' settings in the policy statement:
ecr-public:BatchCheckLayerAvailability ecr-public:CompleteLayerUpload ecr-public:InitiateLayerUpload ecr-public:PutImage ecr-public:UploadLayerPart
Am I missing anything?
Thanks.