Help Center/ API Gateway/ API Reference/ Permissions and Supported Actions/ Permissions and Supported Actions
Updated on 2025-12-09 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 APIG resources. If your HUAWEI ID does not need individual IAM users, you can skip this section.

With IAM, you can control access to specific Huawei Cloud resources. 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

Name

Authorization Using

Permissions

Authorization Method

Scenario

Role/Policy-based authorization

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

Granting 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 the permissions needed 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, configure the condition key g:RequestedRegion for the policy, and then attach the policy to the principals or grant the principals the access permissions to the specified regions. Identity policy-based authorization is more flexible than role/policy-based authorization.

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

Assume that an IAM user wants to call an API to publish an API. With role/policy-based authorization, the IAM user must be granted the permissions allowing for action apig:api:publish. With identity policy-based authorization, the IAM user must be granted the permissions allowing for action apig:api:onlineOrOffline.