Updated on 2025-11-13 GMT+08:00

Using IAM Identity Policies to Grant Access to OA

System-defined permissions in identity-based authorization provided by Identity and Access Management (IAM) let you control access to OA. With IAM, you can:

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

If your Huawei Cloud 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 the system-defined identity policies supported by OA. To grant permissions for other services, learn about all system-defined permissions supported by IAM.

Process Flow

Figure 1 Process of granting OA permissions to a user
  1. On the IAM console, create an IAM user or create a user group.
  2. Attach a system-defined identity policy (CostCenterReadOnlyPolicy as an example) to the user or user group.

    Assign the permissions defined in the system-defined identity policy OAReadOnlyPolicy to the user or 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:

    • On the Huawei Cloud official website, select Optimization Advisor from the drop-down list of your login account. Check whether you have the query permission. If so, the OA ReadOnlyPolicy policy is applied.
    • Add or delete data on any page in OA. If a message appears indicating that you have insufficient permissions to perform the operation, the OA ReadOnlyPolicy policy is in effect.

Example Custom Identity Policy for OA

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

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. The following provides examples of custom OA identity policies.

  • Example 1: Grant the permission to perform a check for check items and obtain the check results.
     {
        "Version": "5.0",
        "Statement": [
            {
                "Effect": "Allow",
                "Action": [
                    "oa:riskItemCheck:createTask",
                    "oa:riskItemCheck:getTaskProgress",
                    "oa:riskItemCheck:getTaskResult",
                ]
            }
        ]
    }
  • Example 2: Grant the permission to delete an architecture diagram, obtain architecture diagram details, create a single risk check task, obtain the progress of a single-item risk check task, and obtain the check results of a single risky item.

    A custom policy can contain the actions of one or multiple services.

    Example policy containing multiple actions:

    {
        "Version": "5.0",
        "Statement": [
            {
                "Effect": "Allow",
                "Action": [
                    "oa:applications:delete",
                    "oa:applications:get"
                ]
            },
            {
                "Effect": "Allow",
                "Action": [
                    "oa:riskItemCheck:createTask",
                    "oa:riskItemCheck:getTaskProgress",
                    "oa:riskItemCheck:getTaskResult"
                ]
            }
        ]
    }