Help Center> GaussDB> User Guide> Permissions Management> Creating a GaussDB(for MySQL) Custom Policy

Creating a GaussDB(for MySQL) Custom Policy

Custom policies can be created to supplement the system-defined policies of GaussDB(for MySQL).

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 GaussDB(for MySQL) custom policies.

Example Custom Policies

  • Example 1: Allowing users to create GaussDB(for MySQL) DB instances
    {
        "Version": "1.1",
        "Statement": [
            {
                "Effect": "Allow",
                "Action": [
                    "gaussdb:instance:create"
                ]
            }
        ]
    }
  • Example 2: Denying GaussDB(for MySQL) DB 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.

    The following method can be used if you need to assign permissions of the GaussDB FullAccess policy to a user but you want to prevent the user from deleting GaussDB(for MySQL) DB instances. Create a custom policy for denying GaussDB(for MySQL) DB instance deletion, and attach both policies to the group to which the user belongs. Then, the user can perform all operations on GaussDB(for MySQL) DB instances except deleting GaussDB(for MySQL) DB instances. The following is an example of a deny policy:

    {
        "Version": "1.1",
        "Statement": [
            {
              "Effect": "Deny"
              "Action": [
                    "gaussdb: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": [  
                                    "gaussdb:instance:create",  
                                    "gaussdb:instance:modify",  
                                    "gaussdb:instance:delete",  
                     "vpc:publicIps:list",  
                     "vpc:publicIps:update"  
                            ],  
                            "Effect": "Allow"  
                    }  
            ]  
    }