Need help?

Our experts have had an average response time of 12.14 minutes in September 2021 to fix urgent issues.

We will keep your servers stable, secure, and fast at all times for one fixed price.

Allow secondary account to Push or Pull images in ECR image repository

by | Sep 1, 2021

Want to allow secondary account to Push or Pull images in ECR image repository? We can help you.

We can push or pull images to or from an Amazon ECR repository in another account.

Here, at Bobcares, we assist our customers with several AWS queries as part of our AWS Support Services.

Today, let us see how we can allow the same.

Allow secondary account to Push or Pull images in ECR image repository

In order to do so, thew are two steps that we need to follow. Here, our Support Techs discuss the same.

  • Create a policy that allows the secondary account to perform API calls against the image repository

1. Initially, we open the Amazon ECR console for the primary account.

2. Then for the repository we want to modify, we select the hyperlinked Repository name.

3. After that, we go to Amazon ECR > Repositories > Permissions.

4. To add a repository policy for the secondary account from primary account, we select, Edit policy JSON.

Here, we can enter the policy into the code editor, and then Save.

Fo example, the below repository policy allows a specific account to push and pull images:

"Version": "2008-10-17",
"Statement": [
"Sid": "AllowPushPull",
"Effect": "Allow",
"Principal": {
"AWS": "arn:aws:iam::account-id:root"
"Action": [

5. Later, in the task definition, we set the image that we want to use with Amazon ECS.

Now, the image is hosted in the primary account’s Amazon ECR repository.

  • Generate a temporary Docker authentication token

We need to do this from the secondary account and perform a test push or pull

In addition, we need to make sure that we use the most recent AWS CLI version.

Unless the secondary account receives a temporary authentication toket, it can’t perform policy actions on the repository.

The token allows it to use Docker push and pull commands against the primary account’s repository.

To troubleshoot issues with Docker, we enable debug mode on the Docker daemon.

1. To generate a Docker authentication token for an account, we run the following command.

We need to replace the aws_account_id with the primary account ID, and replace regionID with the Region ID.

Using the AWS CLI:

aws ecr get-login-password --region regionID | docker login --username AWS --password-stdin

Using AWS Tools for Windows PowerShell:

(Get-ECRLoginCommand).Password | docker login --username AWS --password-stdin
aws ecr get-login-password --region ap-south-1 | docker login --username AWS --password-stdin

WARNING! Your password will be stored unencrypted in /root/.docker/config.json.
Configure a credential helper to remove this warning. See

Login Succeeded

2. Finally, we perform a test image pull or push to the primary account.

[Need help with the procedures? We’d be happy to assist you]


In short, we saw how our Support Techs go about allowing secondary account to Push or Pull images.


Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.



Submit a Comment

Your email address will not be published. Required fields are marked *

Privacy Preference Center


Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]


Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid


Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie


These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.