IAM Access Analyzer

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

The following table lists the actions that you can define in SCP statements for IAM Access Analyzer.

**Table 1** Actions supported by IAM Access Analyzer
Action	Description	Access Level	Resource Type (*: required)	Condition Key
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 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 create an access preview for the specified access analyzer.	read	analyzer *	g:ResourceTag/<tag-key>
AccessAnalyzer:analyzer:listPreviews	Grants permission to retrieve the access preview information for the specified access analyzer.	list	analyzer *	g:ResourceTag/<tag-key>
AccessAnalyzer:analyzer:listPreviewFindings	Grants permission to retrieve the access preview list for the specified access analyzer.	list	analyzer *	g:ResourceTag/<tag-key>
AccessAnalyzer::validatePolicy	Grants permission to validate a policy.	read	-	-

Resources

A resource type indicates the resources that an SCP applies to. If you specify a resource type for any action in Table 2, 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 IAM Access Analyzer.

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

Conditions

IAM Access Analyzer does not support service-specific condition keys in SCPs. It can only use global condition keys applicable to all services. For details, see Global Condition Keys.

Parent topic: Management & Governance

Previous topic: Config

Next topic: Cloud Trace Service (CTS)