Creating a User and Granting Permissions

This section describes how to use Identity and Access Management (IAM) for fine-grained permissions management for your FlexusRDS resources. With IAM, you can:

Create IAM users for employees based on your enterprise's organizational structure. Each IAM user will have their own security credentials for accessing FlexusRDS resources.
Grant only the permissions required for users to perform a specific task.
Entrust a Huawei Cloud account or cloud service to perform efficient O&M on your FlexusRDS resources.

If your Huawei Cloud account does not require individual IAM users, skip this section.

This section describes the procedure for granting permissions (see Figure 1).

Prerequisites

Learn about the permissions (see Permissions) supported by FlexusRDS and choose policies or roles according to your requirements. For the system policies of other services, see System-defined Permissions.

Process Flow

Figure 1 Process for granting FlexusRDS permissions

Create a user group and assign permissions to it.
Create a user group on the IAM console, and attach the RDS ReadOnlyAccess policy to the group.

To use some interconnected services, you also need to configure permissions of such services.

For example, to connect to your DB instance through the console, configure the DAS FullAccess permission of Data Admin Service (DAS) besides RDS ReadOnlyAccess.

Create an IAM user and add it to the user group.
Create a user on the IAM console and add the user to the group created in 1.
Log in and verify permissions.
Log in to the console by using the created user, and verify that the user only has read permissions for FlexusRDS.
- Go to the FlexusRDS console and click Buy FlexusRDS Instance in the upper right corner. If a message appears indicating that you have insufficient permissions to perform the operation, the RDS ReadOnlyAccess policy has already been applied.
- Choose any other service. If a message appears indicating that you have insufficient permissions to access the service, the RDS ReadOnlyAccess policy has already taken effect.