Help Center/ Container Guard Service/ User Guide/ Managing Permissions/ CGS Custom Policies
Updated on 2022-04-06 GMT+08:00
View PDF
Share

CGS Custom Policies

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

Example Custom Policies

  • Example 1: Allowing users to query the cluster list 
    {
    "Version": "1.1",
    "Statement": [
        {
            "Effect": "Allow",
            "Action": [
                "cgs:cluster:list"
            ]
        }
    ]
}
  • Example 2: Preventing users from modifying configurations

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

    The following method can be used if you need to assign permissions of the CGS FullAccess policy to a user but also forbid the user from modifying CGS configurations. Create a custom policy to disallow configuration modification and assign both policies to the group the user belongs to. Then the user can perform all operations on CGS except modifying configurations. The following is an example of a deny policy:

    { 
         "Version": "1.1", 
         "Statement": [ 
                 { 
                         "Action": [ 
                                 "cgs:configuration:operate" 
                         ], 
                         "Effect": "Deny" 
                 } 
         ] 
 }
  • Example 3: Defining permissions for multiple services in a policy

    A custom policy can contain the actions of multiple services that are of the global or project-level type. The following is an example policy containing actions of multiple services:

    {
    "Version": "1.1",
    "Statement": [
        {
            "Effect": "Allow",
            "Action": [
                "cgs:cluster:list",
                "cgs:quota:list"
            ]
        },
        {
            "Effect": "Allow",
            "Action": [
                "hss:accountCracks:unblock",
                "hss:commonIPs:set"
            ]
        }
    ]
}

Parent topic: Managing Permissions