Help Center/ Cloud Operations Center/ API Reference/ Permissions and Supported Actions/ Permissions and Supported Actions
Updated on 2025-10-24 GMT+08:00
View PDF
Share

Permissions and Supported Actions

You can use Identity and Access Management (IAM) for fine-grained permissions management of your COC resources. If your Huawei account does not need individual IAM users, you can skip this section.

With IAM, you can control access to specific resources by granting permissions to principals (IAM users, user groups, agencies or trust agencies). IAM supports role/policy-based authorization and identity policy-based authorization.

The following table describes the differences between these two authorization models.

Table 1 Differences between role/policy-based and identity policy-based authorization

Parameter

Core Relationship

Permission

Authorization Method

Application Scenario

Role/Policy-based authorization

User-permissions-authorization scope
  • System-defined roles
  • System-defined policies
  • Custom policies

Assigning roles or policies to principals

To authorize a user, you need to add it to a user group first and then specify the scope of authorization. It provides a limited number of condition keys and cannot meet the requirements of fine-grained permissions control. This method is suitable for small- and medium-sized enterprises.

Identity policy-based authorization

User-policy
  • System-defined identity policies
  • Custom identity policies
  • Assigning identity policies to principals
  • Attaching identity policies to principals

You can authorize a user by attaching an identity policy to it. User-specific authorization and a variety of key conditions allow for more fine-grained permissions control. However, this model can be hard to set up. It requires a certain amount of expertise and is suitable for medium- and large-sized enterprises.

Assume that you want to grant IAM users permission to create ECSs in CN North-Beijing4 and OBS buckets in CN South-Guangzhou . With role/policy-based authorization, the administrator needs to create two custom policies and assign both to the IAM users. With identity policy-based authorization, the administrator only needs to create one custom policy and configure the condition key g:RequestedRegion for the policy, and then attach the policy to the users or grant the users the permissions.

Policies/Identity policies and actions in the two authorization scenarios are not interoperable. You are advised to use the identity policy-based authorization model.

If you use IAM users in your account to call an API, the IAM users must be granted the required permissions. The required permissions are determined by the actions supported by the API. Only users with the permissions allowing for those actions can call the API successfully.

Assume that an IAM user wants to call an API to query engine information. With policy-based authorization, the IAM user must be granted the permissions allowing for action coc:engine:get. With identity policy-based authorization, the IAM user must be granted the permissions allowing for action coc:engine:get.