Actions Supported by Identity Policy-based Authorization

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 provided 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. 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 What Are the Differences in Access Control Between IAM and Organizations?

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 create an IAM custom identity policy, see Creating a Custom Identity Policy.
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 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 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 DeH, 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 DeH, 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 DeH.

**Table 1** Actions supported by DeH
Action	Description	Access Level	Resource Type (*: required)	Condition Key	Alias
deh:dedicatedHosts:listTags	Grants permissions to query all DeH tags.	list	-	-	deh:dedicatedHostTags:listProjectTags
deh:dedicatedHosts:tagResource	Grants permission to add tags in a batch.	write	dedicatedHost*	g:EnterpriseProjectId g:ResourceTag/<tag-key> g:RequestTag/<tag-key> g:TagKeys	deh:dedicatedHostTags:create
deh:dedicatedHosts:unTagResource	Grants permission to delete tags in a batch.	write	dedicatedHost*	g:EnterpriseProjectId g:ResourceTag/<tag-key> g:RequestTag/<tag-key> g:TagKeys	deh:dedicatedHostTags:delete
deh:dedicatedHosts:listTagsForResource	Grants permissions to query DeH tags.	read	dedicatedHost*	g:EnterpriseProjectId g:ResourceTag/<tag-key>	deh:dedicatedHostTags:list
deh:dedicatedHosts:listResourcesByTag	Grants permissions to query DeHs by tag.	list	-	-	deh:dedicatedHostTags:listDeh
deh:dedicatedHosts:list	Grants permissions to query DeH details.	list	-	g:EnterpriseProjectId	-
deh:dedicatedHosts:getDedicatedHost	Grants permissions to query details about a DeH.	read	dedicatedHost*	g:EnterpriseProjectId g:ResourceTag/<tag-key>	deh:dedicatedHosts:get
deh:dedicatedHosts:updateDedicatedHost	Grants permissions to modify a DeH.	write	dedicatedHost*	g:EnterpriseProjectId g:ResourceTag/<tag-key>	deh:dedicatedHosts:update
deh:dedicatedHosts:getDedicatedHostServers	Grants permissions to query details about VMs on a DeH.	list	dedicatedHost*	g:EnterpriseProjectId g:ResourceTag/<tag-key>	deh:dedicatedHosts:get
deh:dedicatedHostTypes:list	Grants permissions to query DeH types.	list	-	-	-
deh:quotas:get	Grants permissions to query tenant quotas.	read	-	-	-
deh:dedicatedHosts:delete	Grants permissions to release a DeH.	write	dedicatedHost*	g:EnterpriseProjectId g:ResourceTag/<tag-key>	-
deh:dedicatedHosts:create	Grants permissions to create a DeH.	write	dedicatedHost*	g:EnterpriseProjectId g:RequestTag/<tag-key> g:TagKeys	-

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

**Table 2** Actions and dependencies supported by DeH APIs
API	Action	Dependencies
GET /v1.0/{project_id}/dedicated-host-tags/tags	deh:dedicatedHosts:listTags	-
POST /v1.0/{project_id}/dedicated-host-tags/{dedicated_host_id}/tags/action	deh:dedicatedHosts:tagResource	-
POST /v1.0/{project_id}/dedicated-host-tags/{dedicated_host_id}/tags/action	deh:dedicatedHosts:unTagResource	-
GET /v1.0/{project_id}/dedicated-host-tags/{dedicated_host_id}/tags	deh:dedicatedHosts:listTagsForResource	-
POST /v1.0/{project_id}/dedicated-host-tags/resource_instances/action	deh:dedicatedHosts:listResourcesByTag	-
GET /v1.0/{project_id}/dedicated-hosts	deh:dedicatedHosts:list	-
GET /v1.0/{project_id}/dedicated-hosts/{dedicated_host_id}	deh:dedicatedHosts:getDedicatedHost	-
PUT /v1.0/{project_id}/dedicated-hosts/{dedicated_host_id}	deh:dedicatedHosts:updateDedicatedHost	-
GET /v1.0/{project_id}/dedicated-hosts/{dedicated_host_id}/servers	deh:dedicatedHosts:getDedicatedHostServers	-
GET /v1.0/{project_id}/availability-zone/{availability_zone}/dedicated-host-types	deh:dedicatedHostTypes:list	-
GET /v1.0/{project_id}/quota-sets/{tenant_id}	deh:quotas:get	-
DELETE /v1.0/{project_id}/dedicated-hosts/{dedicated_host_id}	deh:dedicatedHosts:delete	-
POST /v1.0/{project_id}/dedicated-hosts	deh:dedicatedHosts:create	-
GET /v1.0/{project_id}/dedicated-host-types	deh:dedicatedHostTypes: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 DeH.