DWS Permissions Management
If you need to assign different permissions to employees in your enterprise to access your DWS resources on Huawei Cloud, 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, to allow software developers in your company to use DWS resources while restricting high-risk operations and resource deletion, you can create IAM users tailored for these developers and grant them only the essential permissions for DWS usage.
If your Huawei Cloud account does not require individual IAM users for permissions management, you can 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 Service Overview.
DWS 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.
DWS is a project-level service deployed and accessed in specific physical regions. To assign DWS 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 DWS, the users need to switch to a region where they have been authorized to use DWS.
- Role: IAM initially provides a coarse-grained authorization mechanism to define permissions based on users' job 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 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 DWS users only the permissions for managing a certain type of DWS resources.
Most policies define permissions based on APIs. For the API actions supported by DWS, see Permissions Policies and Supported Actions.
For how to create a fine-grained permissions policy, see Creating a DWS Custom Policy.
Role/Policy Name |
Description |
Category |
Dependencies |
---|---|---|---|
DWS ReadOnlyAccess |
Read-only permissions for DWS. Users granted these permissions can only view DWS data. |
System-defined policy |
N/A |
DWS FullAccess |
Database administrator permissions for DWS. Users granted these permissions can perform all operations on DWS. |
System-defined policy |
N/A |
DWS Administrator |
Database administrator permissions for DWS. Users granted these permissions can perform operations on all DWS resources.
|
System-defined role |
Dependent on the Tenant Guest and Server Administrator policies, which must be assigned in the same project as the DWS Administrator policy. |
DWS Database Access |
Database access permissions for DWS. Users granted these permissions can generate temporary database user credentials based on IAM users to connect to databases in the data warehouse clusters. |
System-defined role |
Dependent on the DWS Administrator policy, which must be assigned in the same project as the DWS Database Access policy. |
Table 2 lists the common operations supported by each system-defined policy or role of DWS. Choose appropriate policies or roles as required.

- If you use the EIP binding function for the first time in each project of each region, the system prompts you to create the DWSAccessVPC agency to authorize DWS to access VPC. After the authorization is successful, DWS can switch to a healthy VM when the VM bound with the EIP becomes faulty.
- In addition to policy permissions, you may need to grant different operation permissions on resources to users of different roles. For details about operations, such as creating snapshots and restarting clusters, see Syntax of Fine-Grained Permissions Policies.
- By default, only Huawei Cloud accounts or users with Security Administrator permissions can query and create agencies. By default, IAM users in the account do not have the permission to query and create agencies. When an EIP is bound, the binding button is shielded. In this case, you need to contact a user with the DWS Administrator permission to authorize the DWS agency on the current page. For details, see Allowing DWS to Manage Resources.
Operation |
DWS FullAccess |
DWS ReadOnlyAccess |
DWS Administrator |
DWS Database Access |
---|---|---|---|---|
Creating/Restoring clusters |
√ |
x |
√ |
x |
Obtaining the cluster list |
√ |
√ |
√ |
x |
Obtaining the details of a cluster |
√ |
√ |
√ |
x |
Setting automated snapshot policy |
√ |
x |
√ |
x |
Setting security parameters/parameter groups |
√ |
x |
√ |
x |
Restarting clusters |
√ |
x |
√ |
x |
Scaling out clusters |
√ |
x |
√ |
x |
Resetting passwords |
√ |
x |
√ |
x |
Deleting clusters |
√ |
x |
√ |
x |
Configuring maintenance windows |
√ |
x |
√ |
x |
Binding EIPs |
x |
x |
√ |
x |
Unbinding EIPs |
x |
x |
√ |
x |
Creating DNS domain names |
√ |
x |
√ |
x |
Releasing DNS domain names |
√ |
x |
√ |
x |
Modifying DNS domain names |
√ |
x |
√ |
x |
Creating MRS connections |
√ |
x |
√ |
x |
Updating MRS connections |
√ |
x |
√ |
x |
Deleting MRS connections |
√ |
x |
√ |
x |
Adding/Deleting tags |
√ |
x |
√ |
x |
Editing tags |
√ |
x |
√ |
x |
Creating snapshots |
√ |
x |
√ |
x |
Obtaining the snapshot list |
√ |
√ |
√ |
√ |
Deleting snapshots |
√ |
x |
√ |
x |
Copying snapshots |
√ |
x |
√ |
x |
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot