Skip to main content
IAM Policy Map

AmazonEC2ContainerRegistryFullAccess

AdminAWS managedActiveReviewedShow on mapCompare

Summary

Provides administrative access to Amazon ECR resources. The Amazon ECR User Guide says it also grants access to the AWS services Amazon ECR is integrated with, for all Amazon ECR features available in the console.

Permissions imported from the AWS Managed Policy Reference Guide; other sections reviewed against the listed AWS sources.

Identity

ARN
arn:aws:iam::aws:policy/AmazonEC2ContainerRegistryFullAccess
Default version
v3
Created
Last edited
Services
cloudtrail, ecr, iam

Control-plane actions (67)

By access level: 5 List, 4 Permissions management, 23 Read, 2 Tagging, 33 Write.

Control-plane actions by service
ServiceGrantedAccess levels and limitsGranted by
CloudTrail1 of 661 Read; 0 restricted, 0 conditionalcloudtrail:LookupEvents
Elastic Container RegistryAll 65 actions (see the Elastic Container Registry page)5 List, 4 Permissions management, 22 Read, 2 Tagging, 32 Write; 0 restricted, 0 conditionalecr:*
IAM1 of 1901 Write; 1 restricted, 1 conditionaliam:CreateServiceLinkedRole
CloudTrail: 1 actions
  • cloudtrail:LookupEvents (Read)
IAM: 1 actions
  • iam:CreateServiceLinkedRole (Write)

Data-plane actions (0)

By access level: none.

This policy grants no actions in this plane.

Excluded and conditional actions

No patterns are excluded by NotAction or Deny statements.

Resource scope and attachment

Resource scope across granted actions: all-resources.

Can be attached: Yes, to users, groups and roles.

Why this tier

  • Grants at least 80% of the write and permissions-management actions of: ecr (36 of 36).

Guidance

Practical scope

The first statement allows ecr:* and cloudtrail:LookupEvents on Resource "*". The second allows iam:CreateServiceLinkedRole on Resource "*" only when iam:AWSServiceName is replication.ecr.amazonaws.com.

Use cases

  • Give users, groups or roles administrative access to Amazon ECR repositories and images.

Best practices

  • AWS managed policies don't grant least privilege permissions. The IAM User Guide suggests using IAM Access Analyzer to see which permissions principals actually use, then writing a custom policy or generating one with only the required permissions.

Security considerations

  • ecr:* allows every Amazon ECR action on all resources, so it is not limited the way AmazonEC2ContainerRegistryPowerUser is, which the Amazon ECR User Guide says does not allow repository deletion or policy changes.
  • The policy also allows cloudtrail:LookupEvents on all resources and iam:CreateServiceLinkedRole for replication.ecr.amazonaws.com.
  • You cannot change the permissions in an AWS managed policy. If AWS updates the policy, the update affects every user, group and role it is attached to.

Assignment guidance

You can attach this policy to your users, groups and roles. The reference page also links to guidance on creating a permission set using AWS managed policies in IAM Identity Center. The Amazon ECR User Guide says you can attach it to your IAM identities. It fits where administrative access to Amazon ECR is intended. Where read and push access is enough, the guide describes AmazonEC2ContainerRegistryPowerUser.

Related policies

Same service

Same domain

Frequently asked questions

When should I attach AmazonEC2ContainerRegistryFullAccess?
The Amazon ECR User Guide says you can attach it to your IAM identities, and that it grants administrative access to Amazon ECR resources for all Amazon ECR features available in the console. Attach it where that scope is intended.
What does AmazonEC2ContainerRegistryFullAccess grant?
It allows ecr:* and cloudtrail:LookupEvents on all resources, and iam:CreateServiceLinkedRole only for replication.ecr.amazonaws.com.
What are the security risks of AmazonEC2ContainerRegistryFullAccess?
ecr:* allows every Amazon ECR action on all resources, without the limits the guide describes for AmazonEC2ContainerRegistryPowerUser. AWS managed policies don't grant least privilege permissions, and you must consider the security risk of granting principals more permissions than they need. AWS updates to the policy affect every identity it is attached to.

Policy JSON

Download policy.json

{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Effect": "Allow",
      "Action": [
        "ecr:*",
        "cloudtrail:LookupEvents"
      ],
      "Resource": "*"
    },
    {
      "Effect": "Allow",
      "Action": [
        "iam:CreateServiceLinkedRole"
      ],
      "Resource": "*",
      "Condition": {
        "StringEquals": {
          "iam:AWSServiceName": [
            "replication.ecr.amazonaws.com"
          ]
        }
      }
    }
  ]
}

Version history

Current version v3, edited by AWS on 2020-12-05. Version history is recorded from 2026-11-11. Earlier versions are in the IAM console under Policy versions.

Attach snippets

AWS CLI

aws iam attach-role-policy --role-name ROLE_NAME --policy-arn arn:aws:iam::aws:policy/AmazonEC2ContainerRegistryFullAccess
aws iam attach-user-policy --user-name USER_NAME --policy-arn arn:aws:iam::aws:policy/AmazonEC2ContainerRegistryFullAccess
aws iam attach-group-policy --group-name GROUP_NAME --policy-arn arn:aws:iam::aws:policy/AmazonEC2ContainerRegistryFullAccess

CloudFormation

Resources:
  ExampleRole:
    Type: AWS::IAM::Role
    Properties:
      AssumeRolePolicyDocument: {}  # replace with your trust policy
      ManagedPolicyArns:
        - arn:aws:iam::aws:policy/AmazonEC2ContainerRegistryFullAccess

Terraform

resource "aws_iam_role_policy_attachment" "amazonec2containerregistryfullaccess" {
  role       = aws_iam_role.example.name
  policy_arn = "arn:aws:iam::aws:policy/AmazonEC2ContainerRegistryFullAccess"
}

CDK (TypeScript)

role.addManagedPolicy(
  iam.ManagedPolicy.fromAwsManagedPolicyName("AmazonEC2ContainerRegistryFullAccess"),
);

Sources