Help Center/ Ubiquitous Cloud Native Service/ User Guide/ Permissions/ UCS Resource Permissions (IAM-based)/ Identity Policy-based Authorization (New IAM Version)
Updated on 2025-12-22 GMT+08:00
View PDF
Share

Identity Policy-based Authorization (New IAM Version)

Identity policy-based authorization is a capability provided by the new IAM console for more refined, flexible permissions control. For details about the differences between the old and new IAM versions, see Differences Between the Old and New IAM Consoles. If you continue to use the old IAM console, see Role/Policy-based Authorization (Old IAM Version).

System-defined permissions in "Identity Policy-based Authorization" provided by Identity and Access Management (IAM) let you control access to UCS. With IAM, you can:

  • Create IAM users for personnel based on your enterprise's organizational structure. Each IAM user has their own identity credentials for accessing UCS resources.
  • Grant users only the permissions required to perform a given task based on their job responsibilities.
  • Entrust an account or a cloud service to perform efficient O&M on your UCS resources.

If your account meets your permissions requirements, you can skip this section.

Figure 1 shows the process flow of identity policy-based authorization.

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.

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"
      ]
    }
  ]
}