Updated on 2023-09-13 GMT+08:00

Permissions Policies and Supported Actions

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

A policy is a set of permissions defined in JSON format. By default, new IAM users do not have any permissions. You need to add a user to one or more groups and assign permission policies to these groups. The user then inherits permissions from the groups it is a member of. This process is called authorization. After authorization, the user can perform specified operations on Anti-DDoS based on the permissions. For details about the syntax structure and example of a policy, see "Permissions Management" in the Data Replication Service.

There are fine-grained policies and role-based access control (RBAC) policies. An RBAC policy consists of permissions for an entire service. Users in a group with such a policy assigned are granted all of the permissions required for that service. A fine-grained policy consists of API-based permissions for operations on specific resource types. Fine-grained policies, as the name suggests, allow for more fine-grained control than RBAC policies.

Policy-based authorization is useful if you want to allow or deny the access to an API.

An account has all the permissions required to call all APIs, but IAM users must be assigned the required permissions. The permissions required for calling an API are determined by the actions supported by the API. Only users who have been granted permissions allowing the actions can call the API successfully. For example, if an IAM user queries the task list using an API, the user must have been granted permissions that allow the drs:migrationJob:list action.

Supported Actions

Operations supported by a fine-grained policy are specific to APIs. The following describes the headers of the actions provided in this section:

  • Permissions: defined by actions in a custom policy.
  • APIs: REST APIs that can be called in a custom policy.
  • Action: Specific operations that are allowed or denied.
  • Related actions: Actions on which a specific action depends to take effect. When assigning permissions for the action to a user, you also need to assign permissions for the dependent actions.
  • IAM projects or enterprise projects: Type of projects in which policies can be used to grant permissions. A policy can be applied to IAM projects, enterprise projects, or both. Policies that contain actions for both IAM and enterprise projects can be used and take effect for both IAM and Enterprise Management. Policies that only contain actions for IAM projects can be used and only take effect for IAM. For details about the differences between IAM and enterprise projects, see Differences Between IAM and Enterprise Management.