AmazonEC2ContainerRegistryFullAccess

Last Modified

Mar 12, 2026

March 12, 2026 at 09:27 PM UTC

Version

Total Versions

Created

Dec 5, 2020

Actions

Subscribe to updates

Risk

Medium

The same capabilities in a scoped form, resource policy writes, reads across all data, or full access to a whole service. Read from this policy document alone: trust policies, boundaries and SCPs in your account still decide what actually succeeds. How this is assessed

Medium
Can rewrite resource policies and sharing
Grants 4 permissions management actions across 1 service (ecr) on any resource, enough to share resources outside the account.
ecr:deleteregistrypolicyecr:deleterepositorypolicyecr:putregistrypolicyecr:setrepositorypolicy
Use with caution: Turn on IAM Access Analyzer external access findings, and keep account-level guards like S3 Block Public Access enabled.
Medium
Full ecr access on every resource
Uses ecr:* with Resource "*" and no condition, so every action AWS adds to that service later is granted too.
ecr:*
Use with caution: The grant grows every time the service does. For long-lived access, prefer a policy that lists the actions you actually need.

Policy Document

View on GitHub

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34{
  "PolicyVersion": {
    "Document": {
      "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"
              ]
            }
          }
        }
      ]
    },
    "VersionId": "v3",
    "IsDefaultVersion": true,
    "CreateDate": "2020-12-05T00:04:19+00:00"
  }
}