Permissions Management

If you need to assign different permissions to employees in your enterprise to access your CDM 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 cloud resources.

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

If your 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 What Is IAM?.

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

CDM is a project-level service deployed and accessed in specific physical regions. Therefore, CDM permissions are assigned to users in specific regions and only take effect for these regions. If you want the permissions to take effect for all regions, you need to assign the permissions to users in each region. When accessing CDM, the users need to switch to a region where they have been authorized to use the CDM 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, a specific user group is not allowed to delete a cluster. Only basic CDM operations (such as creating and querying jobs) are allowed.

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

**Table 1** System-defined roles and policies supported by CDM
Role/Policy Name	Description	Type
CDM Administrator	Permissions: Administrator permissions for all operations on CDM resources. Users granted these permissions must also be granted permissions of the Tenant Guest and Server Administrator policies. Users granted permissions of the VPC Administrator policy can create VPCs and subnets. Users granted permissions of the Cloud Eye Administrator policy can view monitoring information of CDM clusters.	System role
CDM FullAccess	Administrator permissions for CDM. Users granted these permissions can perform all operations on CDM resources.	System-defined policy
CDM FullAccessExceptEIPUpdating	Users granted these permissions can perform all operations on CDM resources except binding and unbinding EIPs.	System-defined policy
CDM CommonOperations	Users granted these permissions can operate CDM jobs and links.	System-defined policy
CDM ReadOnlyAccess	Read-only permissions for CDM. Users granted these permissions can only view CDM clusters, links, and jobs.	System-defined policy

Table 2 lists the common operations supported by each system-defined policy or role of CDM. Select the policies or roles as required.

**Table 2** Common operations supported by each system-defined policy or role of CDM
Operation	CDM FullAccess	CDM FullAccessExceptEIPUpdating	CDM CommonOperations	CDM ReadOnlyAccess
Creating clusters	√	√	×	×
Binding or unbinding EIPs	√	×	×	×
Querying the cluster list	√	√	√	√
Querying cluster details	√	√	√	√
Restarting clusters	√	√	×	×
Modifying cluster configurations	√	√	×	×
Deleting clusters	√	√	×	×
Creating links	√	√	√	×
Querying links	√	√	√	√
Modifying links	√	√	√	×
Deleting links	√	√	√	×
Creating jobs	√	√	√	×
Querying jobs	√	√	√	√
Modifying jobs	√	√	√	×
Starting jobs	√	√	√	×
Stopping jobs	√	√	√	×
Querying job status	√	√	√	√
Querying job execution history	√	√	√	√
Deleting jobs	√	√	√	×

Previous topic: Quotas

Feedback

Was this page helpful?

Helpful Not helpful

Provide feedback

Thank you very much for your feedback. We will continue working to improve the documentation.

The system is busy. Please try again later.

Which of the following issues have you encountered?

Content is inconsistent with the product UI

Unclear descriptions

Lack of examples or code

Incorrect steps

Can't find what I need

Lack of best practices

Feedback (optional)

0/500

Select at least one type of issue, and enter your comments or suggestions.

Enter a maximum of 500 characters.

Submit Cancel