DEW Permission Management

Updated on 2025-03-04 GMT+08:00

View PDF

If you want to assign different access permissions to employees in an enterprise for the DEW resources purchased on Huawei Cloud, you can use Identity and Access Management (IAM) to perform refined permission 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 account to create IAM users for your employees, and grant permissions to the users to control their access to specific resource types. For example, if you have software developers and you want to assign them the permission to access DEW but not to delete DEW or its resources, then you can create an IAM policy to assign the developers the permission to access DEW but prevent them from deleting DEW related data.

If the Huawei account has met your requirements and you do not need to create an independent IAM user for permission control, skip this section. This will not affect other functions of DEW.

IAM is free. You pay only for the resources in your account. For details about IAM, see IAM Service Overview.

DEW 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 their groups and can perform specified operations on cloud services based on the permissions.

DEW is a project-level service deployed and accessed in specific physical regions. To assign 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. Users need to switch to the authorized region when accessing DEW.

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 must also assign other roles that the permissions depend on 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 DEW users only the permissions for managing a certain type of cloud servers. Most policies contain permissions for specific APIs, and permissions are defined using API actions. For the API actions supported by DEW, see Permissions Policies and Supported Actions.

KMS system policies, KPS system policies, and CSMS system policies list all DEW system permissions.

**Table 1** KMS system policies
Role/Policy	Description	Type	Dependency
KMS Administrator	All permissions of KMS	Role	None
KMS CMKFullAccess	All permissions for KMS keys. Users with these permissions can perform all the operations allowed by policies.	Policy	None
KMS CMKReadOnlyAccess	Read-only permissions for KMS keys. Users with these permissions can perform all the operations allowed by policies.	Policy	None

**Table 2** KPS system policies
Role/Policy	Description	Type	Dependency
DEW KeypairFullAccess	All permissions for KPS. Users with these permissions can perform all the operations allowed by policies.	Policy	None
DEW KeypairReadOnlyAccess	Read-only permissions for KPS in DEW. Users with this permission can only view KPS data.	Policy	None

**Table 3** CSMS system policies
Role/Policy	Description	Type	Dependency
CSMS FullAccess	All permissions for CSMS in DEW. Users with these permissions can perform all the operations allowed by policies.	Policy	None
CSMS ReadOnlyAccess	Read-only permissions for CSMS in DEW. Users with these permissions can perform all the operations allowed by policies.	Policy	None

NOTE:

Key pairs do not support enterprise project authorization. The DEW KeypairFullAccess and DEW KeypairReadOnlyAccess policies cannot be used for enterprise project authorization.

Table 4 lists the common operations supported by each system-defined permission of DEW. Select the permissions as needed.

**Table 4** Common operations supported by each system-defined policy or role of KMS
Operation	KMS Administrator	KMS CMKFullAccess
Create a key	√	√
Enable a key	√	√
Disable a key	√	√
Schedule key deletion	√	√
Cancel scheduled key deletion	√	√
Modify a key alias	√	√
Modify key description	√	√
Generate a random number	√	√
Create a DEK	√	√
Create a plaintext-free DEK	√	√
Encrypt a DEK	√	√
Decrypt a DEK	√	√
Obtain parameters for importing a key	√	√
Import key materials	√	√
Delete key materials	√	√
Create a grant	√	√
Revoke a grant	√	√
Retire a grant	√	√
Query the grant list	√	√
Query retirable grants	√	√
Encrypt data	√	√
Decrypt data	√	√
Send signature messages	√	√
Authenticate signature	√	√
Enable key rotation	√	√
Modify key rotation interval	√	√
Disable key rotation	√	√
Query key rotation status	√	√
Query CMK instances	√	√
Query key tags	√	√
Query project tags	√	√
Batch add or delete key tags	√	√
Add tags to a key	√	√
Delete key tags	√	√
Query the key list	√	√
Query key details	√	√
Query a public key	√	√
Query instance quantity	√	√
Query quotas	√	√
Query the key pair list	x	x
Create or import a key pair	x	x
Query key pairs	x	x
Delete a key pair	x	x
Update key pair description	x	x
Bind a key pair	x	x
Unbind a key pair	x	x
Query a binding task	x	x
Query failed tasks	x	x
Delete all failed tasks	x	x
Delete the failed task	x	x
Query running tasks	x	x

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.See the reply and handling status in My Cloud VOC.

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

For any further questions, feel free to contact us through the chatbot.

Chatbot

DEW Permission Management

DEW Permissions

Related Links

Feedback

Was this page helpful?

Feedback