Skip to main content

Accessing Amazon ECR

In this section we will configure Amazon Elastic Container Registry access for Anyscale clusters. This is useful if you want to launch Clusters with custom images stored in a private registry. This consists of two steps:

  1. The IAM Role used by Anyscale Clusters need the correct policies to read from ECR.
  2. The repository in ECR must grant access to the given IAM Role.

Attach AmazonEC2ContainerRegistryReadOnly to the Cluster Node Role

Refer to Manage IAM Roles to determine the name of the IAM Role that Anyscale Clusters are assigned.

  1. Look in the Permissions policies section of your Role. If the role is assigned AmazonEC2ContainerRegistryReadOnly, no further action is required. If it does not, continue to set up the correct policies.
  1. Click Add Permissions and select Attach policies.
  1. Search for AmazonEC2ContainerRegistryReadOnly and select the policy.
  1. Click Attach policies.

Grant the Cluster Node Role access to a private ECR repository

  1. Search for the Cluster Node Role on the AWS IAM page and select it.
  1. Find and copy the ARN.
  1. Search for the private repo that you want to grant access to on the AWS ECR page and select it.
  1. Navigate to the Permissions section.
  1. Select Edit JSON Policy.
  1. Add the Role ARN from step 2 into the <REPLACE_WITH_ARN> field in the JSON below.
"Version": "2012-10-17",
"Statement": [
"Sid": "AllowPull",
"Effect": "Allow",
"Principal": {
"Action": [

Once this step is completed, nodes launched by Anyscale should have access to your private registry.