Help Center> Distributed Message Service for Kafka> User Guide> Permissions Management> DMS for Kafka Custom Policies
View PDF

DMS for Kafka Custom Policies

Custom policies can be created to supplement the system-defined policies of DMS for Kafka. For the actions that can be added for 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 operation details, see Creating a Custom Policy. The following section contains examples of common DMS for Kafka custom policies.

  • DMS for Kafka permissions policies are based on DMS. Therefore, when assigning permissions, select DMS permissions 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 instances 
    {
    "Version": "1.1",
    "Statement": [
        {
            "Effect": "Allow",
            "Action": [
                "
                     dms:instance:delete
                     dms:instance:modifyStatus
                 "
            ]
        }
    ]
}
  • Example 2: Denying 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.

    You can use the following method to assign permissions of the DMS FullAccess policy to a user while preventing the user from deleting instances. Create a custom policy for denying instance deletion, and attach both policies to the group to which the user belongs. The user can then perform all operations on DMS for Kafka except deleting instances. The following is an example deny policy:

    {
        "Version": "1.1",
        "Statement": [
                {
                        "Effect": "Deny",
                        "Action": [
                                "dms:instance:delete"
                        ]
                }
        ]
}
Parent topic: Permissions Management