Permissions Management

If you need to assign different permissions to employees in your enterprise to access your DCS resources, IAM is a good choice for fine-grained permissions management. IAM provides identity authentication, permissions management, and access control, helping you secure access to your HUAWEI CLOUD resources.

With IAM, you can use your Huawei Cloud account to create IAM users for your employees, and assign permissions to the users to control their access to specific resource types. For example, some software developers in your enterprise need to use DCS resources but should not be allowed to delete DCS instances or perform any other high-risk operations. In this scenario, you can create IAM users for the software developers and grant them only the permissions required for using DCS resources.

If your Huawei Cloud account does not require individual IAM users for permissions management, skip this section.

IAM can be used free of charge. You pay only for the resources in your account. For more information about IAM, see the IAM Service Overview.

DCS Permissions

By default, new IAM users do not have permissions assigned. You need to add a user to one or more groups, and attach permissions policies or roles to these groups. Users inherit permissions from the groups to which they are added and can perform specified operations on cloud services based on the permissions.

DCS is a project-level service deployed and accessed in specific physical regions. To assign DCS permissions to a user group, specify the scope as region-specific projects and select projects for the permissions to take effect. If All projects is selected, the permissions will take effect for the user group in all region-specific projects. When accessing DCS, the users need to switch to a region where they have been authorized to use this service.

You can grant users permissions by using roles and policies.

Roles: A type of coarse-grained authorization mechanism that defines permissions related to user responsibilities. This mechanism provides only a limited number of service-level roles for authorization. When using roles to grant permissions, you need to also assign other roles on which the permissions depend to take effect. However, roles are not an ideal choice for fine-grained authorization and secure access control.
Policies: A type of fine-grained authorization mechanism that defines permissions required to perform operations on specific cloud resources under certain conditions. This mechanism allows for more flexible policy-based authorization, meeting requirements for secure access control. For example, you can grant DCS users only the permissions for operating DCS instances. Most policies define permissions based on APIs. For the API actions supported by DCS, see Permissions Policies and Supported Actions.

Table 1 lists all the system-defined roles and policies supported by DCS.

**Table 1** System-defined roles and policies supported by DCS
Role/Policy Name	Description	Type	Dependency
DCS FullAccess	All permissions for DCS. Users granted these permissions can operate and use all DCS instances.	System-defined policy	Actions required for buying professional instances: iam:permissions:listRolesForAgencyOnProject iam:agencies:listAgenciesiam:roles:listRoles iam:permissions:grantRoleToAgencyOnProject iam:agencies:createAgency iam:agencies:deleteAgency
DCS UserAccess	Common user permissions for DCS, excluding permissions for creating, modifying, deleting DCS instances and modifying instance specifications.	System-defined policy	None
DCS ReadOnlyAccess	Read-only permissions for DCS. Users granted these permissions can only view DCS instance data.	System-defined policy	None
DCS Administrator	Administrator permissions for DCS. Users granted these permissions can operate and use all DCS instances.	System-defined role	The Server Administrator and Tenant Guest roles need to be assigned in the same project.
DCS AgencyAccess	Permissions to assign to DCS agencies. These permissions are used by a tenant to delegate DCS to perform the following operations on tenant resources when necessary. They are irrelevant to the operations performed by authorized users. Querying a subnet Querying the subnet list Querying a port Querying the port list Updating a port Creating a port	System-defined policy	None

The DCS UserAccess policy is different from the DCS FullAccess policy. If you configure both of them, you cannot create, modify, delete, or scale DCS instances because deny statements will take precedence over allowed statements.

Table 2 lists the common operations supported by each system policy of DCS. Please choose proper system policies according to this table.

**Table 2** Common operations supported by each system policy
Operation	DCS FullAccess	DCS UserAccess	DCS ReadOnlyAccess	DCS Administrator
Modifying instance configuration parameters	√	√	×	√
Deleting background tasks	√	√	×	√
Accessing instances using Web CLI	√	√	×	√
Modifying instance running status	√	√	×	√
Expanding instance capacity	√	×	×	√
Changing instance passwords	√	√	×	√
Modifying DCS instances	√	×	×	√
Performing a master/standby switchover	√	√	×	√
Backing up instance data	√	√	×	√
Analyzing big keys or hot keys	√	√	×	√
Creating DCS instances	√	×	×	√
Deleting instance backup files	√	√	×	√
Restoring instance data	√	√	×	√
Resetting instance passwords	√	√	×	√
Migrating instance data	√	√	×	√
Downloading instance backup data	√	√	×	√
Deleting DCS instances	√	×	×	√
Querying instance configuration parameters	√	√	√	√
Querying instance restoration logs	√	√	√	√
Querying instance backup logs	√	√	√	√
Querying DCS instances	√	√	√	√
Querying instance background tasks	√	√	√	√
Querying all instances	√	√	√	√
Operating slow queries	√	√	√	√