DBSS Custom Policies

Examples of Custom Policies

• Example 1: Allowing a user to query the database audit list

  {
      "Version": "1.1",
      "Statement": [
          {
              "Effect": "Allow",
              "Action": [
                  "dbss:auditInstance:list"
              ]
          }
      ]
  }

• Example 2: Denying database audit instance deletion

  A deny policy must be used together with other policies. 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 DBSS FullAccess policy to a user but also forbid the user from deleting database audit instances. Create a custom policy to disallow audit instance deletion and assign both policies to the group the user belongs to. Then the user can perform all operations on DBSS except deleting database audit instances. The following is an example of a deny policy:

  { 
           "Version": "1.1", 
           "Statement": [ 
                   { 
                           "Action": [ 
                                   "dbss:auditInstance:delete" 
                           ], 
                           "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": [
                  "dbss:defendInstance:eipOperate",
                  "dbss:auditInstance:getSpecification"
              ]
          },
          {
              "Effect": "Allow",
              "Action": [
                  "hss:accountCracks:unblock",
                  "hss:commonIPs:set"
              ]
          }
      ]
  }