Actions Supported by Identity Policy-based Authorization

IAM provides system-defined identity policies to define typical cloud service permissions. 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.

For details about how to use these elements to edit an IAM custom identity policy, see Creating a Custom Identity Policy.
For details about how to use these elements to edit a custom SCP, see Creating an SCP.

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 Live, 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 Live, 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 Live.

**Table 1** Actions supported by Live
Action	Description	Access Level	Resource Type (*: required)	Condition Key	Alias
live:ott:createChannel	Grants permission to create channel.	Write	-	-	-
live:ott:listChannel	Grants permission to get channel list.	List	-	-	-
live:ott:deleteChannel	Grants permission to delete channel.	Write	-	-	-
live:ott:updateChannelEndpoint	Grants permission to modify channel endpoint.	Write	-	-	-
live:ott:updateChannelInput	Grants permission to modify channel input imformation.	Write	-	-	-
live:ott:updateChannelRecord	Grants permission to modify channel record settings.	Write	-	-	-
live:ott:updateChannelGeneralInfo	Grants permission to modify channel general information.	Write	-	-	-
live:ott:updateChannelState	Grants permission to modify channel state.	Write	-	-	-
live:ott:modifyChannelTranscodings	Grants permission to modify channel transcodings.	Write	-	-	-
live:ott:getDimsInfo	Grants permission to get dimension Information list.	List	-	-	-
live:ott:listCesInstances	Grants permission to query instance information.	List	-	-	-
live:ott:createFlow	Grants permission to create flow.	Write	-	-	-
live:ott:listFlow	Grants permission to get flow list.	List	-	-	-
live:ott:getFlowDetail	Grants permission to get flow detail.	Read	-	-	-
live:ott:deleteFlow	Grants permission to delete flow.	Write	-	-	-
live:ott:updateFlowStatusStart	Grants permission to update flow status to start.	Write	-	-	-
live:ott:updateFlowStatusStop	Grants permission to update flow status to stop.	Write	-	-	-
live:ott:updateFlowSource	Grants permission to update flow source.	Write	-	-	-
live:ott:createFlowOutput	Grants permission to create flow output.	Write	-	-	-
live:ott:deleteFlowOutput	Grants permission to delete flow output.	Write	-	-	-
live:ott:showFlowOutput	Grants permission to get flow output.	List	-	-	-
live:ott:updateFlowOutput	Grants permission to update flow output.	Write	-	-	-
live:ott:statistic	Grants permission to query channel statistic.	List	-	-	-

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

**Table 2** Actions and dependencies supported by Live APIs
API	Action	Dependencies
POST /v1/{project_id}/ott/channels	live:ott:createChannel	-
GET /v1/{project_id}/ott/channels	live:ott:listChannel	-
DELETE /v1/{project_id}/ott/channels	live:ott:deleteChannel	-
PUT /v1/{project_id}/ott/channels/endpoints	live:ott:updateChannelEndpoint	-
PUT /v1/{project_id}/ott/channels/input	live:ott:updateChannelInput	-
PUT /v1/{project_id}/ott/channels/record-settings	live:ott:updateChannelRecord	-
PUT /v1/{project_id}/ott/channels/general	live:ott:updateChannelGeneralInfo	-
PUT /v1/{project_id}/ott/channels/state	live:ott:updateChannelState	-
PUT /v1/{project_id}/ott/channels/encorder-settings	live:ott:modifyChannelTranscodings	-
GET /v1/{project_id}/ott/dims-info	live:ott:getDimsInfo	-
POST /v1/{project_id}/ott/instances	live:ott:listCesInstances	-
POST /v1/{project_id}/flows	live:ott:createFlow	-
GET /v1/{project_id}/flows	live:ott:listFlow	-
DELETE /v1/{project_id}/flows	live:ott:deleteFlow	-
GET /v1/{project_id}/flows/detail	live:ott:getFlowDetail	-
PUT /v1/{project_id}/flows/start	live:ott:updateFlowStatusStart	-
PUT /v1/{project_id}/flows/stop	live:ott:updateFlowStatusStop	-
PUT /v1/{project_id}/flows/sources	live:ott:updateFlowSource	-
POST /v1/{project_id}/flows/outputs	live:ott:createFlowOutput	-
DELETE /v1/{project_id}/flows/outputs	live:ott:deleteFlowOutput	-
GET /v1/{project_id}/flows/outputs	live:ott:showFlowOutput	-
PUT /v1/{project_id}/flows/outputs	live:ott:updateFlowOutput	-
POST /v1/{project_id}/ott/channels/statistic	live:ott:statistic	-

Resources

Live does not support resource-level authorization. To allow access to Live, use a wildcard (*) in the Resource element of the identity policy, indicating that the identity policy will be applied to all resources.

Conditions

Live 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: Permissions and Supported Actions

Previous topic: Actions Supported by Policy-based Authorization

Next topic: Appendix