Identity Policy-based Authorization (New IAM Version)

Prerequisites

• Before granting permissions, learn about UCS system-defined permissions. To grant permissions for other services, learn about all system-defined permissions supported by IAM.
• A user with the Security Administrator role (for example, your account) has all IAM permissions except role switching. Only these users can view user groups and their permissions on the Permissions page on the UCS console.
• If a service control policy in an organization is used for permissions control, the request for creating yearly/monthly resources cannot be intercepted. For example, if an SCP policy for intercepting ECS creation is configured, yearly/monthly ECSs can still be created on UCS.

Configuration Description

On the UCS console, when you choose Permissions > Add Permission to create a user or user group, you will be directed to the IAM console to complete the process. After the user or user group is created and the permissions are configured, you can view the information on the Permissions page of the cluster or fleet. This section describes the operations in IAM.

Process Flow

Figure 1 Process of granting UCS permissions

1. .

   On the IAM console, create a user or user group.

   

   UCS is a global service deployed for all regions. When granting permissions, set the authorization scope to All resources.

2. Attach a system-defined identity policy to the user or user group.

   Grant the permissions defined in the system-defined identity policy UCSReadOnlyPolicy to the user or user group, or attach the system-defined identity policy to it.

3. Log in as the IAM user and verify permissions.

   In the authorized region, perform the following operations:

   • Choose Service List > Ubiquitous Cloud Native Service. In the navigation pane, choose Infrastructure > Fleets. Create a fleet or register a cluster. If a message appears indicating that you have insufficient permissions to perform the operation, the UCSReadOnlyPolicy policy is in effect.
   • Choose another service from Service List. If a message appears indicating that you have insufficient permissions to access the service, the UCSReadOnlyPolicy policy is in effect.

Identity Policies

The system-defined identity policies preset for UCS in IAM are UCSFullAccessPolicy, UCSCommonOperationsPolicy, and UCSReadOnlyPolicy.

• UCSFullAccessPolicy: administrator permissions for UCS. Users with these permissions can perform all operations on UCS, including creating permission policies and security policies.
• UCSCommonOperationsPolicy: common operation permissions for UCS. Users with these permissions can create workloads, distribute traffic, and perform other operations.
• UCSReadOnlyPolicy: read-only permissions for UCS.

Least-Privilege Permissions for UCS Functions

Services on Huawei Cloud are interdependent, so UCS depends on other cloud services to implement some functions (such as image repositories and domain name resolution). The three system-defined identity policies in Identity Policies are often used together with the roles or policies of other cloud services for refined authorization. When granting permissions to IAM users, the administrator must comply with the principle of least privilege. Table 1 lists the least-privilege permissions required by the Administrator, Operator, and Viewer roles to use UCS functions.

• If your Huawei Cloud account logs in to the UCS console for the first time, you need to grant permissions to the account. UCS will create an agency named ucs_admin_trust for you in IAM. Do not delete or modify the agency.
• If no permissions are granted to the user group that an IAM user belongs to, access to the UCS console will be denied. Grant permissions by referring to Table 1.
• UCSFullAccessPolicy does not have the RBAC permissions of CCE clusters. You need to go to the Permissions page to grant permissions for CCE clusters as described in the following table.

Example Custom Identity Policies

You can create custom identity policies to supplement the system-defined identity policies of UCS. For details about actions supported in custom identity policies, see Permissions and Supported Actions.

To create a custom identity 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 Identity Policy and Attaching It to a Principal.

When creating a custom identity policy, use the Resource element to specify the resources the identity policy applies to and use the Condition element (service-specific condition keys) to control when the identity policy is in effect. The following provides examples of custom UCS identity policies.

• Example 1: Grant permission to create a cluster.

  {
    "Version": "5.0",
    "Statement": [
      {
        "Effect": "Allow",
        "Action": [
          "ucs:clusters:createCluster"
        ]
      }
    ]
  }

• Example 2: Create a custom identity policy containing multiple actions.

  A custom identity policy can contain the actions of one or more services. Example identity policy containing multiple actions:

  {
    "Version": "5.0",
    "Statement": [
      {
        "Effect": "Allow",
        "Action": [
          "ucs:clustergroups:createFleet",
          "ucs:clustergroups:deleteFleet"
        ]
      },
      {
        "Effect": "Deny",
        "Action": [
          "ucs:addons:delete"
        ]
      }
    ]
  }