You need to enable JavaScript to run this app.
Container Registry

Container Registry

Copy page
Download PDF
Authorization management
Adding system policies
Copy page
Download PDF
Adding system policies
CR supports authorizing IAM (Identity and Access Management) users to enable multi-user collaborative management of CR resources. This topic describes how to authorize IAM users to use instances.​
Background​
This topic describes how to authorize IAM users to access CR instances quickly via system-preset policies. For operations related to custom policies, see Adding custom policies.​
A policy is a method of describing the access control capabilities of IAM. IAM supports the following two types of permission policies:​
  • System-preset policies: The policies are created by the system in a centralized manner. You can only use but cannot modify them, and the version updates of these policies are maintained by the system.​
  • User-defined policies: You can create, update, and delete the policies. The version updates of these policies are maintained by yourself.​
Prerequisites​
Procedure​
  1. Log in to the IAM console .​
  1. Create an IAM user and attach the following policies to the user. For methods to create users and attach policies, see Creating users and authorizing access. For more details about policies, see Managing policies.​
  • ​
    Policy​
    Description​
    CRFullAccess​
    This policy allows read and write access to CR. Policy details are as follows:​
    ​
    {​
    "Statement": [​
    {​
    "Effect": "Allow",​
    "Action": [​
    "cr:*",​
    "vpc:Describe*",​
    "artifacts:*",​
    "bill_volcano_engine:CheckPurchasePermission",​
    "bill_volcano_engine:CalculateV2",​
    "bill_volcano_engine:ListConfiguration",​
    "bill_volcano_engine:GetBalanceStatus",​
    "bill_volcano_engine:ListResourcePackage",​
    "storage_ebs:CalculatePrice"​
    ],​
    "Resource": [​
    "*"​
    ]​
    }​
    ]​
    }​
    ​
    CRReadOnlyAccess​
    This policy allows read-only access to CR. Policy details are as follows:​
    ​
    {​
    "Statement": [​
    {​
    "Effect": "Allow",​
    "Action": [​
    "cr:List*",​
    "cr:Get*",​
    "cr:Pull*",​
    "cr:SetUser",​
    "artifacts:Get*",​
    "artifacts:List*",​
    "artifacts:pull",​
    "artifacts:*Credential",​
    "bill_volcano_engine:CheckPurchasePermission",​
    "bill_volcano_engine:CalculateV2",​
    "bill_volcano_engine:ListConfiguration",​
    "bill_volcano_engine:GetBalanceStatus",​
    "bill_volcano_engine:ListResourcePackage",​
    "storage_ebs:CalculatePrice"​
    ],​
    "Resource": [​
    "*"​
    ]​
    }​
    ]​
    }​
    ​
    ​
  1. Authorize the user with the ServiceRoleForCR role. For authorization methods, see Managing roles. Role details are as follows.​
warning​
After authorization, the role will appear on the role list in the IAM console. If you delete the role, it will make cross-service access unavailable. Please proceed with caution.​
  • ​
    Role​
    Description​
    ServiceRoleForCR​
    CR policy for TOS access.​
    • Associated policy: ServiceRolePolicyForCR​
    ​
    {​
    "Statement": [​
    {​
    "Effect": "Allow",​
    "Action": [​
    "vpc:DescribeVpcs",​
    "vpc:DescribeSubnets",​
    "vpc:DescribeSecurityGroups",​
    "vpc:CreateNetworkInterface",​
    "vpc:DeleteNetworkInterface",​
    "vpc:DescribeNetworkInterfaces",​
    "vpc:CreateNetworkInterfacePermission",​
    "vpc:DeleteNetworkInterfacePermission",​
    "vpc:DescribeNetworkInterfacePermissions",​
    "vpc:DescribeVpcAttributes",​
    "vpc:DescribeSubnetAttributes",​
    "vpc:DescribeNetworkInterfaceAttributes",​
    "vpc:AttachNetworkInterface",​
    "vpc:DetachNetworkInterface",​
    "vpc:AssociateTrunkInterface",​
    "vpc:DisassociateTrunkInterface",​
    "vpc:DescribeTrunkAssociations",​
    "private_zone:CreatePrivateZone",​
    "private_zone:UpdatePrivateZone",​
    "private_zone:DeletePrivateZone",​
    "private_zone:QueryPrivateZone",​
    "private_zone:ListPrivateZones",​
    "private_zone:CreateRecord",​
    "private_zone:DeleteRecord",​
    "private_zone:ListRecords",​
    "private_zone:UpdateRecord",​
    "private_zone:BatchCreateRecord",​
    "private_zone:BatchDeleteRecord",​
    "dns:ListZones",​
    "dns:ListRecords",​
    "dns:CreateRecord",​
    "dns:DeleteRecord",​
    "dns:UpdateRecord",​
    "certificate_service:CertificateGetInstance",​
    "tls:CreateProject",​
    "tls:ModifyProject",​
    "tls:DescribeProject",​
    "tls:DescribeProjects",​
    "tls:CreateTopic",​
    "tls:ModifyTopic",​
    "tls:DeleteTopic",​
    "tls:DescribeTopics",​
    "tls:DescribeTopic",​
    "tls:CreateIndex",​
    "tls:ModifyIndex",​
    "tls:DescribeIndex",​
    "tls:PutLogs",​
    "tls:CreateDashboard",​
    "tls:ModifyDashboard",​
    "tls:DeleteDashboard",​
    "tls:DescribeDashboard",​
    "tls:DescribeDashboards",​
    "tls:GetAccountStatus",​
    "kms:DescribeKey",​
    "kms:AsymmetricSign"​
    ],​
    "Resource": [​
    "*"​
    ]​
    }​
    ]​
    }​
    ​
    • Trust relationship: CR​
    ​
    {​
    "Statement": [​
    {​
    "Effect": "Allow",​
    "Action": [​
    "sts:AssumeRole"​
    ],​
    "Principal": {​
    "Service": [​
    "cr"​
    ]​
    }​
    }​
    ]​
    }​
    ​
    ​
​
Last updated: 2026.09.23 14:37:20