If you want to assign different access permissions to employees in an enterprise for the DEW resources purchased on the cloud platform, you can use Identity and Access Management (IAM) to perform refined permission management. IAM provides identity authentication, permissions management, and access control, helping you securely access your cloud service resources.
With IAM, you can use your account to create IAM users for your employees, and grant permissions to control their access to specific resource types. For example, some software developers in your enterprise need to use DEW resources but must not delete them or perform any high-risk operations. To achieve this result, you can create IAM users for the software developers and grant them only the permissions required for using DEW resources.
If the system account has met your requirements and you do not need to create an independent IAM user for permission control, then you can skip this section. This will not affect other functions of DEW.
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 KMS.
You can grant users permissions by using roles and policies.
Role/Policy | Description | Type |
|---|---|---|
KMS Administrator | Administrator permissions for the encryption key | Role |
KMS CMKFullAccess | All permissions for the encryption keys | Policy |
KMS CMKReadOnlyAccess | Read-only permission for encryption keys | Policy |
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 |
Role/Policy | Description | Type | Dependency |
|---|---|---|---|
CSMS FullAccess | All permissions of CSMS in DEW. Users with these permissions can perform all the operations allowed by policies. | Policy | None |
CSMS ReadOnlyAccess | Read-only permissions of CSMS in DEW. Users with these permissions can perform all the operations allowed by policies. | Policy | None |
Table 4 lists the common operations supported by each system-defined permission of DEW. Select the permissions as needed.
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 | √ | √ |
Query the grant list | √ | √ |
Query retirable grants | √ | √ |
Encrypt data | √ | √ |
Decrypt data | √ | √ |
Query CMK instances | √ | √ |
Query the key list | √ | √ |
Query key details | √ | √ |
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 |