IAM Access Analyzer Identity Policy-based Authorization Reference

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 IAM Access Analyzer, 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 IAM Access Analyzer, 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 IAM Access Analyzer.

**Table 1** Actions supported by IAM Access Analyzer
Action	Description	Access Level	Resource Type (*: required)	Condition Key	Alias
AccessAnalyzer:analyzer:create	Grants permission to create an access analyzer.	Write	analyzer *	-	-
AccessAnalyzer:analyzer:create	Grants permission to create an access analyzer.	Write	-	g:RequestTag/<tag-key> g:TagKeys	-
AccessAnalyzer:analyzer:get	Grants permission to retrieve the access analyzer information.	Read	analyzer *	g:ResourceTag/<tag-key>	-
AccessAnalyzer:analyzer:list	Grants permission to retrieve the access analyzer list.	List	analyzer *	-	-
AccessAnalyzer:analyzer:delete	Grants permission to delete an access analyzer.	Write	analyzer *	g:ResourceTag/<tag-key>	-
AccessAnalyzer:analyzer:update	Grants permission to update the specified access analyzer.	Write	analyzer *	g:ResourceTag/<tag-key>	-
AccessAnalyzer:analyzer:scan	Grants permission to start a scan for the specified access analyzer.	Write	analyzer *	g:ResourceTag/<tag-key>	-
AccessAnalyzer:analyzer:getFinding	Grants permission to retrieve findings.	Read	analyzer *	g:ResourceTag/<tag-key>	-
AccessAnalyzer:analyzer:listFindings	Grants permission to retrieve the finding list.	List	analyzer *	g:ResourceTag/<tag-key>	-
AccessAnalyzer:analyzer:updateFindings	Grants permission to update the findings.	Write	analyzer *	g:ResourceTag/<tag-key>	-
AccessAnalyzer::tagResource	Grants permission to add a tag to a resource.	Tagging	analyzer *	g:ResourceTag/<tag-key>	-
AccessAnalyzer::tagResource	Grants permission to add a tag to a resource.	Tagging	-	g:RequestTag/<tag-key> g:TagKeys	-
AccessAnalyzer::untagResource	Grants permission to remove a tag from a resource.	Tagging	analyzer *	g:ResourceTag/<tag-key>	-
AccessAnalyzer::untagResource	Grants permission to remove a tag from a resource.	Tagging	-	g:TagKeys	-
AccessAnalyzer:archiveRule:create	Grants permission to create an archive rule for the specified access analyzer.	Write	archiveRule *	-	-
AccessAnalyzer:archiveRule:get	Grants permission to retrieve the archive rule for the specified access analyzer.	Read	archiveRule *	-	-
AccessAnalyzer:archiveRule:list	Grants permission to retrieve the archive rule list for the specified access analyzer.	List	archiveRule *	-	-
AccessAnalyzer:archiveRule:update	Grants permission to modify the archive rule for the specified access analyzer.	Write	archiveRule *	-	-
AccessAnalyzer:archiveRule:delete	Grants permission to delete the archive rule for the specified access analyzer.	Write	archiveRule *	-	-
AccessAnalyzer:archiveRule:apply	Grants permission to apply an archive rule.	Write	archiveRule *	-	-
AccessAnalyzer:analyzer:createPreview	Grants permission to create an access preview for the specified access analyzer.	Write	analyzer *	g:ResourceTag/<tag-key>	-
AccessAnalyzer:analyzer:getPreview	Grants permission to retrieve the access preview information for the specified access analyzer.	Read	analyzer *	g:ResourceTag/<tag-key>	-
AccessAnalyzer:analyzer:listPreviews	Grants permission to retrieve the access preview list for the specified access analyzer.	List	analyzer *	g:ResourceTag/<tag-key>	-
AccessAnalyzer:analyzer:listPreviewFindings	Grants permission to retrieve the preview finding list for the specified access analyzer.	List	analyzer *	g:ResourceTag/<tag-key>	-
AccessAnalyzer:analyzer:createResourceConfigurations	Grants permission to create or update resource configurations.	Write	analyzer *	g:ResourceTag/<tag-key>	-
AccessAnalyzer:analyzer:listResourceConfigurations	Grants permission to retrieve the list for resource configurations.	List	analyzer *	g:ResourceTag/<tag-key>	-
AccessAnalyzer:analyzer:deleteResourceConfigurations	Grants permission to delete the resource configurations.	Write	analyzer *	g:ResourceTag/<tag-key>	-
AccessAnalyzer::validatePolicy	Grants permission to validate a policy.	Read	-	-	-
AccessAnalyzer::checkNoNewAccess	Grants permission to check whether the updated policy has new access permissions.	Read	-	-	-
AccessAnalyzer:notificationSetting:list	Grants permission to retrieve the notification setting list.	Read	notificationSetting *	-	-
AccessAnalyzer:notificationSetting:create	Grants permission to create a notification setting.	Write	notificationSetting *	-	-
AccessAnalyzer:notificationSetting:get	Grants permission to retrieve the notification setting.	Read	notificationSetting *	-	-
AccessAnalyzer:notificationSetting:update	Grants permission to modify the notification setting.	Write	notificationSetting *	-	-
AccessAnalyzer:notificationSetting:delete	Grants permission to delete the notification setting.	Write	notificationSetting *	-	-

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

**Table 2** Actions and dependencies supported by IAM Access Analyzer APIs
API	Action	Dependencies
POST /v5/analyzers	AccessAnalyzer:analyzer:create	iam:agencies:createServiceLinkedAgencyV5
GET /v5/analyzers/{analyzer_id}	AccessAnalyzer:analyzer:get	-
GET /v5/analyzers	AccessAnalyzer:analyzer:list	-
DELETE /v5/analyzers/{analyzer_id}	AccessAnalyzer:analyzer:delete	-
PUT /v5/analyzers/{analyzer_id}	AccessAnalyzer:analyzer:update	-
POST /v5/analyzers/{analyzer_id}/scan	AccessAnalyzer:analyzer:scan	-
GET /v5/analyzers/{analyzer_id}/findings/{finding_id}	AccessAnalyzer:analyzer:getFinding	-
POST /v5/analyzers/{analyzer_id}/findings	AccessAnalyzer:analyzer:listFindings	-
PUT /v5/analyzers/{analyzer_id}/findings	AccessAnalyzer:analyzer:updateFindings	-
POST /v5/{resource_type}/{resource_id}/tags/create	AccessAnalyzer::tagResource	-
POST /v5/{resource_type}/{resource_id}/tags/delete	AccessAnalyzer::untagResource	-
POST /v5/analyzers/{analyzer_id}/archive-rules	AccessAnalyzer:archiveRule:create	-
GET /v5/analyzers/{analyzer_id}/archive-rules/{archive_rule_id}	AccessAnalyzer:archiveRule:get	-
GET /v5/analyzers/{analyzer_id}/archive-rules	AccessAnalyzer:archiveRule:list	-
PUT /v5/analyzers/{analyzer_id}/archive-rules/{archive_rule_id}	AccessAnalyzer:archiveRule:update	-
DELETE /v5/analyzers/{analyzer_id}/archive-rules/{archive_rule_id}	AccessAnalyzer:archiveRule:delete	-
POST /v5/analyzers/{analyzer_id}/archive-rules/{archive_rule_id}/apply	AccessAnalyzer:archiveRule:apply	-
POST /v5/analyzers/{analyzer_id}/access-previews	AccessAnalyzer:analyzer:createPreview	-
GET /v5/analyzers/{analyzer_id}/access-previews/{access_preview_id}	AccessAnalyzer:analyzer:getPreview	-
GET /v5/analyzers/{analyzer_id}/access-previews	AccessAnalyzer:analyzer:listPreviews	-
POST /v5/analyzers/{analyzer_id}/access-previews/{access_preview_id}/findings	AccessAnalyzer:analyzer:listPreviewFindings	-
POST /v5/analyzers/{analyzer_id}/resource-configurations/create	AccessAnalyzer:analyzer:createResourceConfigurations	-
GET /v5/analyzers/{analyzer_id}/resource-configurations	AccessAnalyzer:analyzer:listResourceConfigurations	-
POST /v5/analyzers/{analyzer_id}/resource-configurations/delete	AccessAnalyzer:analyzer:deleteResourceConfigurations	-
POST /v5/policies/validate	AccessAnalyzer::validatePolicy	-
POST /v5/policies/check-no-new-access	AccessAnalyzer::checkNoNewAccess	-
GET /v5/notification-settings	AccessAnalyzer:notificationSetting:list	-
POST /v5/notification-settings	AccessAnalyzer:notificationSetting:create	-
GET /v5/notification-settings/{notification_setting_id}	AccessAnalyzer:notificationSetting:get	-
PUT /v5/notification-settings/{notification_setting_id}	AccessAnalyzer:notificationSetting:update	-
DELETE /v5/notification-settings/{notification_setting_id}	AccessAnalyzer:notificationSetting:delete	-

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 IAM Access Analyzer.

**Table 3** Resource types supported by IAM Access Analyzer
Resource Type	URN
analyzer	AccessAnalyzer:<region>:<account-id>:analyzer:<analyzer-id>
notificationSetting	AccessAnalyzer:<region>:<account-id>:notificationSetting:<notification-setting-id>
archiveRule	AccessAnalyzer:<region>:<account-id>:archiveRule:<analyzer-id>/<archive-rule-id>

Conditions

IAM Access Analyzer 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: STS Identity Policy-based Authorization Reference

Next topic: Appendix