Help Center> Distributed Message Service> Service Overview> Permissions Management
View PDF

Permissions Management

If you need to assign different permissions to employees in your enterprise to access your DMS 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, and assign permissions to the users to control their access to specific resources. For example, some software developers in your enterprise need to use DMS resources but should not be allowed to delete queues 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 DMS 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.

DMS Kafka permissions policies are based on DMS. Therefore, when assigning Kafka permissions, select DMS permissions policies.

DMS 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.

DMS is a project-level service deployed and accessed in specific physical regions. To assign DMS 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 ECS, 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 DMS users only the permissions for managing DMS resources.

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

Table 1 System-defined roles and policies supported by DMS

Role/Policy Name

Description

Type

Dependency

DMS FullAccess

Administrator permissions for DMS. Users granted these permissions can perform all operations on DMS.

System-defined policy

None

DMS UserAccess

Common user permissions for DMS, excluding permissions for creating, modifying, deleting, scaling up instances and dumping.

System-defined policy

None

DMS ReadOnlyAccess

Read-only permissions for DMS. Users granted these permissions can only view DMS data.

System-defined policy

None

DMS Administrator

Administrator permissions for DMS logical tenancy. Users granted these permissions can perform all operations on DMS queues.

System-defined role

None
  • Currently, DMS uses only the DMS Administrator role.
  • DMS FullAccess, DMS UserAccess, and DMS ReadOnlyAccess policies are used to control the operation permissions for DMS for Kafka and DMS for RabbitMQ.

Helpful Links