Help Center> > API Reference > Permissions Policies and Supported Actions >Introduction


This chapter describes fine-grained permissions management for your Application Operations Management (AOM). If your HUAWEI CLOUD account does not need individual Identity and Access Management (IAM) users, then you may skip over this chapter.

A policy is a set of permissions defined in JSON format. By default, new IAM users do not have any permissions assigned. You need to add a user to one or more groups, and assign permissions policies to these groups. The user then inherits permissions from the groups it is a member of. This process is called authorization. After authorization, the user can perform specified operations on AOM based on the permissions. For details about the policy syntax structure and example, see Policy Syntax.

There are fine-grained policies and role-based access control (RBAC) policies. An RBAC policy consists of permissions for an entire service. Users in a group with such a policy assigned are granted all of the permissions required for that service. A fine-grained policy consists of API-based permissions for operations on specific resource types. Fine-grained policies, as the name suggests, allow for more fine-grained control than RBAC policies.

  • AOM supports fine-grained policies only.
  • Fine-grained policies are currently available for open beta testing. You can apply to use the fine-grained access control function free of charge. For more information, see Fine-grained Policy.

A HUAWEI CLOUD account has all of the permissions required to call all APIs, but IAM users must have the required permissions specifically assigned. The permissions required for calling an API are determined by the actions supported by the API. Only users who have been granted permissions can call the API successfully. For example, if an IAM user queries metrics using an API, the user must have been granted permissions that allow the aom:metric:get action.

Supported Actions

Operations supported by a fine-grained policy are specific to APIs. The following describes the headers of the action tables provided in this chapter:

  • Permissions: Defined by actions in a custom policy.
  • Actions: Added to a custom policy to control permissions for specific operations.
  • Authorization Scope: A custom policy can be applied to IAM projects or enterprise projects or both. Policies that contain actions supporting both IAM and enterprise projects can be assigned to user groups and take effect in both IAM and Enterprise Management. Policies that only contain actions supporting IAM projects can be assigned to user groups and only take effect for IAM. Such policies will not take effect if they are assigned to user groups in Enterprise Management. For details about the differences between IAM and enterprise projects, see What Are the Differences Between IAM and Enterprise Management?.
  • APIs: REST APIs that can be called in a custom policy.

AOM supports the following actions that can be defined in custom policies:

  • Monitoring Actions: includes the actions supported by monitoring APIs, such as the APIs for querying metrics; querying and adding monitoring data; adding, modifying, querying, and deleting threshold rules; adding, modifying, querying, and deleting service discovery rules.
  • Auto Scaling Actions: includes the actions supported by auto scaling APIs, such as the APIs for creating, deleting, and modifying policies; querying one or all policies; modifying and querying policy group attributes.
  • Log Actions: includes the actions supported by log APIs, such as the API for querying logs.
  • APM Actions: includes the actions supported by APM APIs, such as the APIs for querying the application list, service list, service instance list, service transaction list, tracing, and tracing details.