Permissions Policies and Supported Actions
This chapter describes fine-grained permissions management for your DCS. If your account does not need individual IAM users, you can skip the configurations described in this chapter.
By default, new IAM users do not have any permissions assigned. You need to add a user to one or more groups, and assign policies or roles to these groups. The user then inherits permissions from the groups it is a member of. This process is called authorization. After authorization, the user can perform specified operations on cloud services based on the permissions.
You can grant users permissions by using roles and policies. Roles are a type of coarse-grained authorization mechanism that defines permissions related to user responsibilities. Policies define API-based permissions for operations on specific resources under certain conditions, allowing for more fine-grained, secure access control of cloud resources.
You can use policies to allow or deny access to specific APIs.
An account has all of the permissions required to call all APIs, but IAM users must have the required permissions specifically assigned. The permissions required for calling an API are determined by the actions supported by the API. Only users who have been granted permissions allowing the actions can call the API successfully. For example, if an IAM user wants to query ECSs using an API, the user must have been granted permissions that allow the dcs:servers:list action.
Supported Actions
DCS provides system-defined policies, which can be directly used in IAM. You can also create custom policies to supplement system-defined policies for more refined access control. Actions supported by policies are specific to APIs. Common concepts related to policies include:
- Permissions: Allow or deny certain operations.
- APIs: REST APIs that can be called in a custom policy.
- Actions: Added to a custom policy to control permissions for specific operations.
- Dependent actions: When assigning permissions for an action, you also need to assign permissions for the dependent actions.
- IAM and enterprise projects: Type of projects for which an action will take effect. Policies that contain actions supporting both IAM and enterprise projects can be assigned to user groups and take effect in both IAM and Enterprise Management. Policies that only contain actions supporting IAM projects can be assigned to user groups and only take effect for IAM. Such policies will not take effect if they are assigned to user groups in Enterprise Project. Administrators can check whether an action supports IAM projects or enterprise projects in the action list. The check mark (√) indicates that the action supports the project and the cross symbol (×) indicates that the action does not support the project.
The following table lists the API actions supported by DCS.
Permissions |
Action |
API |
IAM Project |
Enterprise Project |
---|---|---|---|---|
Creating DCS instances |
dcs:instance:create |
POST /v1.0/{project_id}/instances |
√ |
√ |
Querying an instance |
dcs:instance:get |
GET /v1.0/{project_id}/instances/{instance_id} |
√ |
√ |
Modifying the information about an instance |
dcs:instance:modify |
PUT /v1.0/{project_id}/instances/{instance_id} |
√ |
√ |
Deleting an instance |
dcs:instance:delete |
DELETE /v1.0/{project_id}/instances/{instance_id} |
√ |
√ |
Expanding instance capacity |
dcs:instance:scale |
POST /v1.0/{project_id}/instances/{instance_id}/extend |
√ |
√ |
Querying all instances |
dcs:instance:list |
GET /v1.0/{project_id}/instances |
√ |
√ |
Querying instance configuration parameters |
dcs:instance:getConfiguration |
GET /v1.0/{project_id}/instances/{instance_id}/configs |
√ |
√ |
Modifying instance configuration parameters |
dcs:instance:modifyConfigureation |
PUT /v1.0/{project_id}/instances/{instance_id}/configs |
√ |
√ |
Restarting an instance or clearing instance data |
dcs:instance:modifyStatus |
PUT /v1.0/{project_id}/instances/status |
√ |
√ |
Changing the instance password |
dcs:instance:modifyAuthInfo |
PUT /v1.0/{project_id}/instances/{instance_id}/password |
√ |
√ |
Backing up an instance |
dcs:instance:backupData |
POST /v1.0/{project_id}/instances/{instance_id}/backups |
√ |
√ |
Restoring an instance |
dcs:instance:restoreData |
POST /v1.0/{project_id}/instances/{instance_id}/restores |
√ |
√ |
Querying backup records |
dcs:instance:getDataBackupLog |
GET /v1.0/{project_id}/instances/{instance_id}/backups |
√ |
√ |
Querying restoration records |
dcs:instance:getDataRestoreLog |
GET /v1.0/{project_id}/instances/{instance_id}/restores |
√ |
√ |
Deleting backup files |
dcs:instance:deleteDataBackupFile |
DELETE /v1.0/{project_id}/instances/{instance_id}/backups/{backup_id} |
√ |
√ |
Listing background tasks |
dcs:instance:getBackgroundTask |
GET /v1.0/{project_id}/instances/{instance_id}/tasks |
√ |
√ |
Deleting a background task |
dcs:instance:deleteBackgroundTask |
DELETE /v1.0/{project_id}/instances/{instance_id}/tasks/{task_id} |
√ |
√ |
Resetting the instance password |
dcs:instance:resetAuthInfo |
- |
√ |
√ |
Downloading backup files |
dcs:instance:downloadBackupData |
- |
√ |
√ |
Migrating data |
dcs:instance:migrateData |
- |
√ |
√ |
Web CLI |
dcs:instance:webcli |
- |
√ |
√ |
Creating a migration task |
dcs:migrationTask:create |
- |
√ |
X |
Modifying migration task configurations or stopping a migration task |
dcs:migrationTask:modify |
- |
√ |
X |
Deleting a migration task |
dcs:migrationTask:delete |
- |
√ |
X |
Listing migration tasks |
dcs:migrationTask:list |
- |
√ |
X |
Querying details of a data migration task |
dcs:migrationTask:get |
- |
√ |
X |
Diagnosing an instance |
dcs:instance:diagnosis |
- |
√ |
√ |
Viewing parameter templates |
dcs:template:list |
- |
√ |
X |
Creating a parameter template |
dcs:template:create |
- |
√ |
X |
Performing a master/standby switchover |
dcs:instance:swap |
- |
√ |
√ |
Modifying the whitelist of an instance |
dcs:whitelist:modify |
- |
√ |
√ |
Obtaining the whitelist of an instance |
dcs:whitelist:list |
- |
√ |
√ |
Creating a user for accessing an instance |
dcs:aclaccount:create |
- |
√ |
√ |
Deleting an instance user |
dcs:aclaccount:delete |
- |
√ |
√ |
Modifying the information about an instance user |
dcs:aclaccount:modify |
- |
√ |
√ |
Obtaining the list of instance users |
dcs:aclaccount:list |
- |
√ |
√ |
Querying slow logs |
dcs:slowlog:list |
- |
√ |
√ |
Viewing parameter templates |
dcs:template:get |
- |
√ |
X |
Viewing audit logs |
dcs:auditlog:get |
- |
√ |
√ |
Querying SSL encryption of an instance |
dcs:ssl:get |
- |
√ |
√ |
Updating domain names |
dcs:domainname:rebuild |
- |
√ |
√ |
Switching IP addresses |
dcs:migrationTask:exchangeIp |
- |
√ |
X |
Rolling back IP address switching |
dcs:migrationTask:rollbackIp |
- |
√ |
X |
Killing Redis sessions |
dcs:clients:kill |
- |
√ |
√ |
Modifying a parameter template |
dcs:template:modify |
- |
√ |
X |
Enabling or disabling public domain name resolution |
dcs:publicdomainname:update |
- |
√ |
√ |
Deleting a parameter template |
dcs:template:delete |
- |
√ |
X |
Releasing historical domain names |
dcs:histroydomainname:release |
- |
√ |
√ |
Upgrading the instance version |
dcs:instance:upgrade |
- |
√ |
√ |
Analyzing big or hot keys |
dcs:instance:analyze |
- |
√ |
√ |
Enabling or disabling audit logging |
dcs:auditlog:modify |
- |
√ |
√ |
Enabling or disabling client IP pass-through |
dcs:clientiptrans:modify |
- |
√ |
√ |
Modifying SSL encryption for an instance |
dcs:ssl:modify |
- |
√ |
√ |
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