Updated on 2022-09-15 GMT+08:00

DCS Custom Policies

Custom policies can be created to supplement the system-defined policies of DCS. For the actions that can be added to custom policies, see Permissions Policies and Supported Actions.

You can create custom policies in either of the following ways:

  • Visual editor: Select cloud services, actions, resources, and request conditions. This does not require knowledge of policy syntax.
  • JSON: Edit JSON policies from scratch or based on an existing policy.

For details, see Creating a Custom Policy. The following section contains examples of common DCS custom policies.

Due to data caching, a policy involving OBS actions will take effect five minutes after it is attached to a user, user group, or project.

Example Custom Policies

  • Example 1: Allowing users to delete and restart DCS instances and clear data of an instance
    {
        "Version": "1.1",
        "Statement": [
            {
                "Effect": "Allow",
                "Action": [
                    "
                         dcs:instance:delete
                         dcs:instance:modifyStatus
                     "
                ]
            }
        ]
    }
  • Example 2: Denying DCS instance deletion

    A policy with only "Deny" permissions must be used in conjunction with other policies to take effect. If the permissions assigned to a user contain both "Allow" and "Deny", the "Deny" permissions take precedence over the "Allow" permissions.

    For example, if you want to assign all of the permissions of the DCS FullAccess policy to a user, except for deleting DCS instances, you can create a custom policy to deny only DCS instance deletion. When you apply both the DCS FullAccess policy and the custom policy denying DCS instance deletion, since "Deny" always takes precedence over "Allow", the "Deny" will be applied for that one conflicting permission. The user will then be able to perform all operations on DCS instances except deleting DCS instances. The following is an example of a deny policy:

    {
            "Version": "1.1",
            "Statement": [
                    {
                            "Effect": "Deny",
                            "Action": [
                                    "dcs:instance:delete"
                            ]
                    }
            ]
    }