Application Operations Management (AOM)

The Organizations service provides Service Control Policies (SCPs) to set access control policies.

SCPs do not actually grant any permissions to a principal. They only set the permissions boundary for the principal. When SCPs are attached to a member account or an organizational unit (OU), they do not directly grant permissions to that member account or OU. Instead, the SCPs just determine what permissions are available for that member account or the member accounts under that OU.

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

For details about how to use these elements to create a custom SCP, see Creating an SCP.

Actions

Actions are specific operations that are allowed or denied in an SCP.

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 SCP.
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 SCP statements.
- If this column includes a resource type, you must specify the URN in the Resource element of your 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 SCP 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 following table lists the actions that you can define in SCP statements for AOM.

**Table 1** Actions supported by AOM
Action	Description	Access Level	Resource Type (*: Required)	Condition Key
aom:metric:delete	Grants permission to delete monitoring configurations.	write	-	-
aom:icmgr:get	Grants permission to query the collection component version list.	read	-	-
aom:agency:get	Grants permission to query agency permissions.	read	-	-
aom:icmgr:list	Grants permission to query the collection component version list.	list	-	-
aom:metric:list	Grants permission to query metrics.	list	-	-
aom:metric:put	Grants permission to report metrics.	write	-	-
aom:discoveryRule:set	Grants permission to create or update the service discovery rule list.	write	-	-
aom:discoveryRule:delete	Grants permission to delete the service discovery rule list.	write	-	-
aom:discoveryRule:list	Grants permission to query the service discovery rule list.	list	-	-
aom:alarmRule:create	Grants permission to create alarm rules.	write	alarmRule *	g:ResourceTag/<tag-key>
aom:alarmRule:create	Grants permission to create alarm rules.	write	-	g:TagKeys g:RequestTag/<tag-key>
aom:alarmRule:list	Grants permission to query the alarm rule list.	list	-	-
aom:alarmRule:update	Grants permission to update alarm rules.	write	-	-
aom:alarmRule:delete	Grants permission to delete alarm rules.	write	alarmRule *	g:ResourceTag/<tag-key>
aom:alarm:put	Grants permission to report alarms and events.	write	-	-
aom:alarm:list	Grants permission to query alarms and events.	list	-	-
aom:alarmRule:get	Grants permission to query alarm rules.	read	-	-
aom:view:create	Grants permission to create a dashboard.	write	-	-
aom:event2AlarmRule:list	Grants permission to query the event alarm rule list.	list	-	-
aom:event2AlarmRule:create	Grants permission to create event alarm rules.	write	-	-
aom:event2AlarmRule:update	Grants permission to update event alarm rules.	write	-	-
aom:event2AlarmRule:delete	Grants permission to delete event alarm rules.	write	-	-
aom:muteRule:create	Grants permission to create silence rules.	write	-	-
aom:muteRule:list	Grants permission to query the silence rule list.	list	-	-
aom:muteRule:update	Grants permission to update silence rules.	write	-	-
aom:muteRule:delete	Grants permission to delete silence rules.	write	-	-
aom:actionRule:get	Grants permission to query action rules.	read	-	-
aom:actionRule:list	Grants permission to query the action rule list.	list	-	-
aom:actionRule:create	Grants permission to create action rules.	write	-	-
aom:actionRule:update	Grants permission to modify action rules.	write	-	-
aom:actionRule:delete	Grants permission to delete action rules.	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 /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	-
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.	-

Resources

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

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