Using IAM Roles or Policies to Grant Access to TaurusDB

Prerequisites

Before granting permissions to user groups, learn about system-defined permissions in Role/Policy-based Authorization for TaurusDB. To grant permissions for other services, learn about all system-defined permissions supported by IAM.

Process Flow

Figure 1 Process of granting TaurusDB permissions using role/policy-based authorization

1. On the IAM console, create a user group and grant it permissions (TaurusDB ReadOnlyAccess as an example).
2. Create an IAM user and add it to the created user group.
3. Log in as the IAM user and verify permissions.

   In the authorized region, perform the following operations:

   • Choose Service List > Databases > TaurusDB. Then click Buy DB Instance on the TaurusDB console. If a message appears indicating that you have insufficient permissions to perform the operation, the TaurusDB ReadOnlyAccess policy is in effect.
   • Choose another service from the service list. If a message appears indicating that you have insufficient permissions to access the service, the TaurusDB ReadOnlyAccess policy is in effect.

Example Custom Policies

You can create custom policies to supplement the system-defined policies of TaurusDB. For details about actions supported in custom policies, see Actions Supported by Policy-based Authorization.

To create a custom policy, choose either visual editor or JSON.

• Visual editor: Select cloud services, actions, resources, and request conditions. This does not require knowledge of policy grammar.
• JSON: Create a JSON policy or edit an existing one.

For details, see Creating a Custom Policy. The following lists examples of common TaurusDB custom policies.

• Example 1: Grant permission to create a TaurusDB instance

  {
      "Version": "1.1",
      "Statement": [
          {
              "Effect": "Allow",
              "Action": [
                  "gaussdb:instance:create"
              ]
          }
      ]
  }

• Example 2: Grant permission to deny TaurusDB instance deletion.

  A policy with only "Deny" permissions must be used together with other policies. If the permissions granted to an IAM user contain both "Allow" and "Deny", the "Deny" permissions take precedence over the "Allow" permissions.

  Assume that you want to grant the permissions of the TaurusDB FullAccess policy to a user but want to prevent them from deleting TaurusDB instances. You can create a custom policy for denying TaurusDB instance deletion, and attach this policy together with the TaurusDB FullAccess policy to the user. As an explicit deny in any policy overrides any allows, the user can perform all operations on TaurusDB instances excepting deleting them. Example policy denying instance deletion:

  {
      "Version": "1.1",
      "Statement": [
          {
            "Effect": "Deny"
            "Action": [
                  "gaussdb:instance:delete"
              ],
            }
      ]
  }

• Example 3: Create a custom policy containing multiple actions.

  A custom policy can contain the actions of one or multiple services that are of the same type (global or project-level). Example policy containing multiple actions:

  {  
          "Version": "1.1",  
          "Statement": [  
                  {  
                          "Action": [  
                                  "gaussdb:instance:create",  
                                  "gaussdb:instance:modify",  
                                  "gaussdb:instance:delete",  
                   "vpc:publicIps:list",  
                   "vpc:publicIps:update"  
                          ],  
                          "Effect": "Allow"  
                  }  
          ]  
  }