Introduction

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

New IAM users do not have any permissions assigned by default. You need to first add them to one or more groups and attach policies or roles to these groups. The users then inherit permissions from the groups and can perform specified operations on cloud services based on the permissions they have been assigned.

You can grant users permissions using roles and policies. Roles are provided by IAM to define service-based permissions that match user's job responsibilities. Policies define API-based permissions for operations on specific resources under certain conditions, allowing for more fine-grained, secure access control of cloud resources.

If you want to allow or deny the access to an API, use policy-based authorization.

Each account has all the permissions required to call all APIs, but IAM users must be granted 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 wants to query EVS disks using an API, the user must have been granted permissions that allow the evs:volumes:list action.

Supported Actions

EVS provides system-defined policies that can be directly used in IAM. You can also create custom policies to supplement system-defined policies for more refined access control. Operations supported by policies are specific to APIs. The following are common concepts related to policies:

Permissions: statements in a policy that allow or deny certain operations
APIs: REST APIs that can be called by a user who has been granted specific permissions
Actions: specific operations that are allowed or denied
Dependencies: actions which a specific action depends on. When allowing an action for a user, you also need to allow any existing action dependencies for that user.
IAM projects/Enterprise projects: the authorization scope of a custom policy. A custom policy can be applied to IAM projects or enterprise projects or both. Policies that contain actions for both IAM and enterprise projects can be used and applied for both IAM and Enterprise Management. Policies that contain actions only for IAM projects can be used and applied to IAM only. For details about the differences between IAM and enterprise management, see Differences Between IAM and Enterprise Management

EVS supports the following actions that can be defined in custom policies:

API version query actions (API Version Query), including actions supported by EVS version query APIs, such as the APIs for querying API versions.
Disk actions (Disk), including actions supported by EVS disk APIs, such as the APIs for creating a disk, querying disks, deleting a disk, and updating a disk.
Actions of disk actions (Disk Action), including actions supported by EVS disk actions, such as the APIs for expanding the capacity of a disk, exporting a disk as an image, and setting read-only flag for a disk.
Snapshot actions (Snapshot), including actions supported by EVS snapshot APIs, such as the APIs for creating a snapshot, querying snapshots, updating a snapshot, and deleting a snapshot.
Tag actions (Tag), including actions supported by EVS tag APIs, such as the APIs for deleting tags by key, batch adding tags, batch deleting tags, and querying tags.
Disk transfer actions (Disk Transfer), including actions supported by EVS disk transfer APIs, such as the APIs for creating a disk transfer, querying disk transfers, accepting a disk transfer, and deleting a disk transfer.