Help Center/ System Permissions/ User Guide/ Identity Policy–based Authorization/ Management & Governance/ Application Operations Management
Updated on 2025-11-06 GMT+08:00
View PDF
Share

Application Operations Management

IAM provides system-defined identity policies to define common actions supported by cloud services. You can also create custom identity policies using the actions supported by cloud services for more refined access control.

In addition to IAM, the Organizations service also provides Service Control Policies (SCPs) to set access control policies.

SCPs do not actually grant any permissions to an entity. They only set the permissions boundary for the entity. When SCPs are attached to an organizational unit (OU) or a member account, the SCPs do not directly grant permissions to that OU or member account. Instead, the SCPs only determine what permissions are available for that member account or those member accounts under that OU. The granted permissions can be applied only if they are allowed by the SCPs.

To learn more about how IAM is different from Organizations for access control, see How IAM Is Different from Organizations for Access Control?.

This section describes the elements used by IAM custom identity policies and Organizations SCPs. The elements include actions, resources, and conditions.

Actions

Actions are specific operations that are allowed or denied in an identity policy.

  • The Access Level column describes how the action is classified (List, Read, or Write). This classification helps you understand the level of access that an action grants when you use it in an identity policy.
  • The Resource Type column indicates whether the action supports resource-level permissions.
    • You can use a wildcard (*) to indicate all resource types. If this column is empty (-), the action does not support resource-level permissions and you must specify all resources ("*") in your identity policy statements.
    • If this column includes a resource type, you must specify the URN in the Resource element of your identity policy statements.
    • Required resources are marked with asterisks (*) in the table. If you specify a resource in a statement using this action, then it must be of this type.

    For details about the resource types defined by AOM, see Resources.

  • The Condition Key column contains keys that you can specify in the Condition element of an identity policy statement.
    • If the Resource Type column has values for an action, the condition key takes effect only for the listed resource types.
    • If the Resource Type column is empty (-) for an action, the condition key takes effect for all resources that action supports.
    • If the Condition Key column is empty (-) for an action, the action does not support any condition keys.

    For details about the condition keys defined by AOM, see Conditions.

  • The Alias column lists the policy actions that are configured in identity policies. With these actions, you can use APIs for policy-based authorization. For details, see Policies and Identity Policies.

The following table lists the actions that you can define in identity policy statements for AOM.

Table 1 Actions supported by AOM

Action

Description

Access Level

Resource Type (*: required)

Condition Key

Alias

aom:view:delete

Grants permission to delete dashboard.

Write

-

-

-

aom:view:get

Grants permission to get dashboard.

Read

-

-

-

aom:metric:delete

Grants permission to delete monitoring configuration.

Write

-

-

-

aom:icmgr:get

Grants permission to get collection component version info.

Read

-

-

-

aom:agency:get

Grants permission to querying agency permissions.

Read

-

-

-

aom:icmgr:list

Grants permission to query ICAgent list.

List

-

-

-

aom:metric:set

Grants permission to modify monitoring configuration.

Write

-

-

-

aom:metric:list

Grants permission to query metric item.

List

-

-

aom:metric:get

aom:metric:put

Grants permission to report metric.

Write

-

-

-

aom:discoveryRule:set

Grants permission to create or update service discovery rule.

Write

-

-

-

aom:discoveryRule:delete

Grants permission to delete service discovery rule.

Write

-

-

-

aom:discoveryRule:list

Grants permission to list service discovery rule.

List

-

-

-

aom:alarmRule:create

Grants permission to create alarm rule.

Write

alarmRule *

g:ResourceTag/<tag-key>

-

-

aom:alarmRule:list

Grants permission to query alarm rule list.

List

-

-

-

aom:alarmRule:update

Grants permission to update alarm rule.

Write

-

-

aom:alarmRule:set

aom:alarmRule:delete

Grants permission to delete alarm rule.

Write

alarmRule *

g:ResourceTag/<tag-key>

-

aom:alarm:put

Grants permission to push alarms and events.

Write

-

-

-

aom:alarmRule:get

Grants permission to query alarm rule.

Read

-

-

-

aom:event2AlarmRule:list

Grants permission to list event to alarm rule.

List

-

-

-

aom:event2AlarmRule:create

Grants permission to create event to alarm rule.

Write

-

-

-

aom:event2AlarmRule:update

Grants permission to update event to alarm rule.

Write

-

-

aom:event2AlarmRule:set

aom:event2AlarmRule:delete

Grants permission to delete event to alarm rule.

Write

-

-

-

aom:muteRule:create

Grants permission to create mute rule.

Write

-

-

-

aom:muteRule:list

Grants permission to list mute rule.

List

-

-

-

aom:muteRule:update

Grants permission to update mute rule.

Write

-

-

-

aom:muteRule:delete

Grants permission to delete mute rule.

Write

-

-

-

aom:actionRule:get

Grants permission to query action rule.

Read

-

-

-

aom:actionRule:list

Grants permission to query action rule list.

List

-

-

-

aom:actionRule:create

Grants permission to create action rule.

Write

-

-

-

aom:actionRule:update

Grants permission to update action rule.

Write

-

-

-

aom:actionRule:delete

Grants permission to delete action rule.

Write

-

-

-

aom:alarm:list

Grants permission to query alarms and events.

List

-

-

-

aom:notificationTemplate:create

Grants permission to create notification template.

Write

-

-

-

aom:notificationTemplate:delete

Grants permission to delete notification template.

Write

-

-

-

aom:notificationTemplate:update

Grants permission to update notification template.

Write

-

-

-

aom:notificationTemplate:list

Grants permission to get notification template list.

List

-

-

-

aom:notificationTemplate:get

Grants permission to get notification template.

Read

-

-

-

aom:alarmRuleTemplate:list

Grants permission to query alarm rule policy V4 list.

List

-

-

-

aom:alarmRuleTemplate:delete

Grants permission to delete alarm rule policy V4.

Write

-

-

-

Each API of AOM usually supports one or more actions. Table 2 lists the supported actions and dependencies.

Table 2 Actions and dependencies supported by AOM APIs

API

Action

Dependencies

DELETE /v2/{project_id}/aom/dashboards/{dashboard_id}

aom:view:delete

-

GET /v2/{project_id}/aom/dashboards

aom:view:get

-

GET /v2/{project_id}/aom/dashboards/{dashboard_id}

aom:view:get

-

DELETE /v2/{project_id}/aom/dashboards-folder/{folder_id}

aom:view:delete

-

GET /v2/{project_id}/aom/dashboards-folder

aom:view:get

-

DELETE /v1/{project_id}/aom/prometheus

aom:metric:delete

-

GET /v1/{project_id}/aom/prometheus

aom:metric:list

-

POST /v1/{project_id}/aom/prometheus

aom:metric:put

-

PUT /v1/{project_id}/aom/prometheus

aom:metric:set

-

POST /v1/{project_id}/{prometheus_instance}/aom/api/v1/rules

aom:metric:put

-

GET /v1/{project_id}/access-code

aom:icmgr:get

-

GET /v1/{project_id}/aom/auth/grant

aom:agency:get

-

GET /v1/{project_id}/{cluster_id}/{namespace}/agents

aom:icmgr:list

-

POST /v2/{project_id}/series

aom:metric:list

-

POST /v2/{project_id}/samples

aom:metric:list

-

GET /v1/{project_id}/aom/api/v1/query_range

aom:metric:list

-

POST /v1/{project_id}/aom/api/v1/query_range

aom:metric:list

-

GET /v1/{project_id}/aom/api/v1/query

aom:metric:list

-

POST /v1/{project_id}/aom/api/v1/query

aom:metric:list

-

GET /v1/{project_id}/aom/api/v1/label/{label_name}/values

aom:metric:list

-

GET /v1/{project_id}/aom/api/v1/labels

aom:metric:list

-

POST /v1/{project_id}/aom/api/v1/labels

aom:metric:list

-

GET /v1/{project_id}/aom/api/v1/metadata

aom:metric:list

-

POST /v1/{project_id}/ams/metrics

aom:metric:list

-

POST /v1/{project_id}/ams/metricdata

aom:metric:list

-

POST /v1/{project_id}/ams/report/metricdata

aom:metric:put

-

PUT /v1/{project_id}/inv/servicediscoveryrules

aom:discoveryRule:set

-

DELETE /v1/{project_id}/inv/servicediscoveryrules

aom:discoveryRule:delete

-

GET /v1/{project_id}/inv/servicediscoveryrules

aom:discoveryRule:list

-

POST /v2/{project_id}/alarm-rules

aom:alarmRule:create

-

GET /v2/{project_id}/alarm-rules

aom:alarmRule:list

-

PUT /v2/{project_id}/alarm-rules

aom:alarmRule:update

-

DELETE /v2/{project_id}/alarm-rules/{alarm_rule_id}

aom:alarmRule:delete

-

GET /v2/{project_id}/alarm-rules/{alarm_rule_id}

aom:alarmRule:get

-

POST /v2/{project_id}/alarm-rules/delete

aom:alarmRule:delete

-

POST /v2/{project_id}/events

aom:alarm:list

-

POST /v2/{project_id}/events/statistic

aom:alarm:list

-

PUT /v2/{project_id}/push/events

aom:alarm:put

-

GET /v2/{project_id}/alarm-notified-histories

aom:alarm:list

-

GET /v2/{project_id}/event2alarm-rule

aom:event2AlarmRule:list

-

POST /v2/{project_id}/event2alarm-rule

aom:event2AlarmRule:create

-

PUT /v2/{project_id}/event2alarm-rule

aom:event2AlarmRule:update

-

DELETE /v2/{project_id}/event2alarm-rule

aom:event2AlarmRule:delete

-

POST /v2/{project_id}/alert/action-rules

aom:actionRule:create

-

GET /v2/{project_id}/alert/action-rules

aom:actionRule:list

-

PUT /v2/{project_id}/alert/action-rules

aom:actionRule:update

-

DELETE /v2/{project_id}/alert/action-rules

aom:actionRule:delete

-

GET /v2/{project_id}/alert/action-rules/{rule_name}

aom:actionRule:get

-

POST /v2/{project_id}/alert/mute-rules

aom:muteRule:create

-

DELETE /v2/{project_id}/alert/mute-rules

aom:muteRule:delete

-

PUT /v2/{project_id}/alert/mute-rules

aom:muteRule:update

-

GET /v2/{project_id}/alert/mute-rules

aom:muteRule:list

-

POST /v4/{project_id}/alarm-rules

aom:alarmRule:create

-

GET /v4/{project_id}/alarm-rules

aom:alarmRule:list

-

DELETE /v4/{project_id}/alarm-rules

aom:alarmRule:delete

NOTE:

The resource type alarmRule of this action applies only to the DELETE /v4/{project_id}/alarm-rules API.

-

POST /v2/{project_id}/events/notification/templates

aom:notificationTemplate:create

-

DELETE /v2/{project_id}/events/notification/templates

aom:notificationTemplate:delete

-

PUT /v2/{project_id}/events/notification/templates

aom:notificationTemplate:update

-

GET /v2/{project_id}/events/notification/templates

aom:notificationTemplate:list

-

GET /v2/{project_id}/events/notification/template/{name}

aom:notificationTemplate:get

-

DELETE /v4/{project_id}/alarm-rules-template

aom:alarmRuleTemplate:delete

-

GET /v4/{project_id}/alarm-rules-template

aom:alarmRuleTemplate:list

-

Resources

A resource type indicates the resources that an identity policy applies to. If you specify a resource type for any action in Table 3, the resource URN must be specified in the identity policy statements using that action, and the identity policy applies only to resources of this type. If no resource type is specified, the Resource element is marked with an asterisk (*) and the identity policy applies to all resources. You can also set condition keys in an identity policy to define resource types.

The following table lists the resource types that you can define in identity policy statements for AOM.

Table 3 Resource types supported by AOM

Resource Type

URN

alarmRule

aom:<region>:<account-id>:alarmRule:<alarm_rule_id>

Conditions

AOM does not support service-specific condition keys in identity policies.It can only use global condition keys applicable to all services. For details, see Global Condition Keys.

Parent topic: Management & Governance