Help Center/ GeminiDB/ GeminiDB Influx API/ Working with GeminiDB Influx API/ Permissions Management/ Creating a Custom Policy
Updated on 2023-11-21 GMT+08:00
View PDF

Creating a Custom Policy

Custom policies can be created to supplement the system-defined policies of GeminiDB. For the actions supported 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 details, Creating a Custom Policy. The following describes examples of common GeminiDB custom policies.

Example Custom Policy

  • Example 1: Allowing users to create GeminiDB instances 
    {
    "Version": "1.1",
    "Statement": [
        {
            "Effect": "Allow",
            "Action": [
                "nosql:instance:create"
            ]
        }
    ]
}
  • Example 2: Deny users the permission to delete GeminiDB instances.

    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 GaussDB NoSQLFullAccess policy to a user but you want to prevent the user from deleting GeminiDB instances. Create a custom policy for denying instance deletion, and attach both policies to the group to which the user belongs. Then, the user can perform all operations on GeminiDB instances except deleting GeminiDB instances. The following is an example of the deny policy:

    {
    "Version": "1.1",
    "Statement": [
        {
          "Effect": "Deny"
          "Action": [
                "nosql:instance:delete"
            ],
          }
    ]
}
  • 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": [  
                {  
                        "Action": [  
                                "nosql:instance:create",  
                                "nosql:instance:rename",  
                                "nosql:instance:delete",  
                                "vpc:publicIps:list",  
                                "vpc:publicIps:update"  
                        ],  
                        "Effect": "Allow"  
                }  
        ]  
}
Parent topic: Permissions Management