Config

Organizations provides your with Service Control Policies for access control.

SCPs do not actually grant any permissions to a principal. They only set the permissions boundary for the principal. 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 in 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 resource URN in the Resource element of your 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 Config, 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 this column is empty (-), the action does not support any condition keys.
For details about the condition keys defined by Config, see Conditions.

The following table lists the actions that you can define in SCP statements for Config.

**Table 1** Actions supported by Config
Action	Description	Access Level	Resource Type (*: Required)	Condition Key
rms:organizationConformancePacks:create	Grants permission to create organization conformance packages.	write	-	-
rms:organizationConformancePacks:get	Grants permission to view organization conformance packages.	read	organizationConformancePacks *	-
rms:organizationConformancePacks:delete	Grants permission to delete organization conformance packages.	write	organizationConformancePacks *	-
rms:organizationConformancePacks:update	Grants permission to update organization conformance packages.	write	organizationConformancePacks *	-
rms:organizationConformancePacks:list	Grants permission to list organization conformance packages.	list	-	-
rms:conformancePacks:create	Grants permission to create conformance packages.	write	-	-
rms:conformancePacks:get	Grants permission to view conformance packages.	read	conformancePacks *	-
rms:conformancePacks:delete	Grants permission to delete conformance packages.	write	conformancePacks *	-
rms:conformancePacks:update	Grants permission to update conformance packages.	write	conformancePacks *	-
rms:conformancePacks:list	Grants permission to list conformance packages.	list	-	-
rms:storedQueries:create	Grants permission to save new advanced queries.	write	-	-
rms:storedQueries:update	Grants permission to update advanced queries.	write	storedQueries *	-
rms:storedQueries:delete	Grants permission to delete advanced query statements.	write	storedQueries *	-
rms:storedQueries:get	Grants permission to view advanced query details.	read	storedQueries *	-
rms:storedQueries:list	Grants permission to list advanced queries.	list	-	-
rms:policyAssignments:create	Grants permission to create rules.	write	-	g:TagKeys g:RequestTag/<tag-key>
rms:policyAssignments:update	Grants permission to update rules.	write	policyAssignments *	g:ResourceTag/<tag-key>
rms:policyAssignments:update	Grants permission to update rules.	write	-	g:TagKeys g:RequestTag/<tag-key>
rms:policyAssignments:delete	Grants permission to delete rules and their evaluation results.	write	policyAssignments *	g:ResourceTag/<tag-key>
rms:policyAssignments:get	Grants permission to view rule details.	read	policyAssignments *	g:ResourceTag/<tag-key>
rms:organizationPolicyAssignments:put	Grants permission to create or update organization rules.	write	-	-
rms:organizationPolicyAssignments:delete	Grants permission to delete specific organization rules and their evaluation results.	write	organizationPolicyAssignments *	-
rms:organizationPolicyAssignments:get	Grants permission to view organization rule details.	read	organizationPolicyAssignments *	-
rms:organizationPolicyAssignments:list	Grants permission to list organization rules.	list	-	-
rms:policyStates:get	Grants permission to list rule evaluation results.	read	policyAssignments	g:ResourceTag/<tag-key>
rms:policyStates:runEvaluation	Grants permission to run specific rules.	write	policyAssignments	g:ResourceTag/<tag-key>
rms:policyStates:update	Grants permission to deliver evaluation results from FunctionGraph Config.	write	-	-
rms:aggregators:create	Grants permission to create aggregators.	write	-	-
rms:aggregators:update	Grants permission to update aggregators.	write	aggregators *	-
rms:aggregators:delete	Grants permission to delete specific aggregators.	write	aggregators *	-
rms:aggregators:list	Grants permission to list aggregators.	list	-	-
rms:aggregators:get	Grants permission to view aggregator details.	read	aggregators *	-
rms:aggregatorResources:list	Grants permission to view aggregated resources.	list	-	-
rms:aggregatorResources:runQuery	Grants permission to run advanced queries for querying attributes of aggregated resources.	list	-	-
rms:aggregatorResources:get	Grants permission to view details of aggregated resources	read	-	-
rms:aggregationAuthorizations:create	Grants permission to create aggregation authorization.	write	aggregationAuthorizations *	-
rms:aggregationAuthorizations:create	Grants permission to create aggregation authorization.	write	-	rms:AuthorizedAccountOrgPath
rms:aggregationAuthorizations:list	Grants permission to list aggregator authorization.	list	-	-
rms:aggregationAuthorizations:delete	Grants permission to revoke aggregation authorization.	write	aggregationAuthorizations *	-
rms:aggregationAuthorizations:delete	Grants permission to revoke aggregation authorization.	write	-	rms:AuthorizedAccountOrgPath
rms:aggregationRequests:delete	Grants permission to delete aggregation requests from other accounts.	write	-	-
rms:aggregationRequests:list	Grants permission to list aggregation requests from other accounts.	list	-	-
rms:trackerConfig:put	Grants permission to enable the resource recorder or modify resource recorder configurations.	write	-	rms:TrackerBucketName rms:TrackerBucketPathPrefix
rms:trackerConfig:delete	Grants permission to disable the resource recorder.	write	-	-
rms:trackerConfig:get	Grants permission to view resource recorder configurations.	read	-	-
rms:schemas:list	Grants permission to view schemas of advanced queries.	list	-	-
rms:policyDefinitions:get	Grants permission to view built-in policies.	list	-	-
rms:resources:getHistory	Grants permission to view resource configuration history.	list	-	-
rms:resources:getRelation	Grants permission to view resource relationships.	list	-	-
rms:resources:get	Grants permission to view details of specific resources.	read	-	-
rms:resources:list	Grants permission to list resources.	list	-	-
rms:resources:runQuery	Grants permission to run advanced queries.	list	-	-
rms:resources:summarize	Grants permission to view resource overview.	list	-	-
rms::tagResource	Grants permission to batch create resource tags.	tagging	policyAssignments	g:ResourceTag/<tag-key>
rms::tagResource	Grants permission to batch create resource tags.	tagging	-	g:RequestTag/<tag-key> g:TagKeys
rms::unTagResource	Grants permission to batch delete resource tags.	tagging	policyAssignments	g:ResourceTag/<tag-key>
rms::unTagResource	Grants permission to batch delete resource tags.	tagging	-	g:RequestTag/<tag-key> g:TagKeys
rms::listTagsForResource	Grants permission to query resource tags.	list	policyAssignments	g:ResourceTag/<tag-key>
rms::listTags	Grants permission to query project tags.	list	-	-
rms::listResourcesByTag	Grants permission to query resources by tag.	list	-	g:TagKeys
rms:policyAssignmentsRemediation:putRemediationConfiguration	Grants permission to add remediation configurations.	write	policyAssignmentsRemediation *	-
rms:policyAssignmentsRemediation:deleteRemediationConfiguration	Grants permission to delete remediation configurations.	write	policyAssignmentsRemediation *	-
rms:policyAssignmentsRemediation:getRemediationConfiguration	Grants permission to check remediation configurations.	read	policyAssignmentsRemediation *	-
rms:policyAssignmentsRemediation:runRemediation	Grants permission to run remediation execution.	write	policyAssignmentsRemediation *	-
rms:policyAssignmentsRemediation:listRemediationExecutionStatuses	Grants permission to check remediation execution status.	list	policyAssignmentsRemediation *	-
rms:policyAssignmentsRemediation:createRemediationExceptions	Grants permission to create remediation exceptions.	write	policyAssignmentsRemediation *	-
rms:policyAssignmentsRemediation:deleteRemediationExceptions	Grants permission to delete remediation exceptions.	write	policyAssignmentsRemediation *	-
rms:policyAssignmentsRemediation:listRemediationExceptions	Grants permission to check remediation exceptions.	list	policyAssignmentsRemediation *	-

A Config API usually supports one or more actions. Table 2 lists actions supported by each API and dependencies of actions.

**Table 2** Actions and dependencies
API	Action	Dependencies
POST /v1/resource-manager/organizations/{organization_id}/conformance-packs	rms:organizationConformancePacks:create	organizations:organizations:get organizations:accounts:list organizations:delegatedAdministrators:list organizations:trustedServices:enable organizations:trustedServices:list
DELETE /v1/resource-manager/organizations/{organization_id}/conformance-packs/{conformance_pack_id}	rms:organizationConformancePacks:delete	organizations:organizations:get
GET /v1/resource-manager/organizations/{organization_id}/conformance-packs	rms:organizationConformancePacks:list	organizations:organizations:get
GET /v1/resource-manager/organizations/{organization_id}/conformance-packs/{conformance_pack_id}	rms:organizationConformancePacks:get	organizations:organizations:get
GET /v1/resource-manager/organizations/{organization_id}/conformance-packs/statuses	rms:organizationConformancePacks:list	organizations:organizations:get
GET /v1/resource-manager/organizations/{organization_id}/conformance-packs/detailed-statuses	rms:organizationConformancePacks:get	organizations:organizations:get
POST /v1/resource-manager/domains/{domain_id}/conformance-packs	rms:conformancePacks:create	rf:stack:createStack rf:stack:getStackMetadata rf:stack:listStackResources
DELETE /v1/resource-manager/domains/{domain_id}/conformance-packs/{conformance_pack_id}	rms:conformancePacks:delete	rf:stack:deleteStack rf:stack:getStackMetadata
GET /v1/resource-manager/domains/{domain_id}/conformance-packs/{conformance_pack_id}	rms:conformancePacks:get	-
GET /v1/resource-manager/domains/{domain_id}/conformance-packs/{conformance_pack_id}/compliance	rms:conformancePacks:get	-
GET /v1/resource-manager/domains/{domain_id}/conformance-packs/{conformance_pack_id}/compliance/details	rms:conformancePacks:get	-
GET /v1/resource-manager/domains/{domain_id}/conformance-packs	rms:conformancePacks:list	-
GET /v1/resource-manager/domains/{domain_id}/conformance-packs/compliance/summary	rms:conformancePacks:list	-
GET /v1/resource-manager/domains/{domain_id}/conformance-packs/scores	rms:conformancePacks:list	-
POST /v1/resource-manager/domains/{domain_id}/stored-queries	rms:storedQueries:create	-
PUT /v1/resource-manager/domains/{domain_id}/stored-queries/{query_id}	rms:storedQueries:update	-
DELETE /v1/resource-manager/domains/{domain_id}/stored-queries/{query_id}	rms:storedQueries:delete	-
GET /v1/resource-manager/domains/{domain_id}/stored-queries/{query_id}	rms:storedQueries:get	-
GET /v1/resource-manager/domains/{domain_id}/stored-queries	rms:storedQueries:list	-
PUT /v1/resource-manager/domains/{domain_id}/policy-assignments	rms:policyAssignments:create	-
DELETE /v1/resource-manager/domains/{domain_id}/policy-assignments/{policy_assignment_id}	rms:policyAssignments:delete	-
GET /v1/resource-manager/domains/{domain_id}/policy-assignments/{policy_assignment_id}	rms:policyAssignments:get	-
GET /v1/resource-manager/domains/{domain_id}/policy-assignments	rms:policyAssignments:get	-
PUT /v1/resource-manager/domains/{domain_id}/policy-assignments/{policy_assignment_id}	rms:policyAssignments:update	-
POST /v1/resource-manager/domains/{domain_id}/policy-assignments/{policy_assignment_id}/disable	rms:policyAssignments:update	-
POST /v1/resource-manager/domains/{domain_id}/policy-assignments/{policy_assignment_id}/enable	rms:policyAssignments:update	-
PUT /v1/resource-manager/organizations/{organization_id}/policy-assignments	rms:organizationPolicyAssignments:put	organizations:organizations:get organizations:accounts:list organizations:delegatedAdministrators:list organizations:trustedServices:enable organizations:trustedServices:list
GET /v1/resource-manager/organizations/{organization_id}/policy-assignments	rms:organizationPolicyAssignments:list	organizations:organizations:get
GET /v1/resource-manager/organizations/{organization_id}/policy-assignments/{organization_policy_assignment_id}	rms:organizationPolicyAssignments:get	organizations:organizations:get
GET /v1/resource-manager/organizations/{organization_id}/policy-assignment-statuses	rms:organizationPolicyAssignments:list	organizations:organizations:get
GET /v1/resource-manager/organizations/{organization_id}/policy-assignment-detailed-status	rms:organizationPolicyAssignments:list	organizations:organizations:get
DELETE /v1/resource-manager/organizations/{organization_id}/policy-assignments/{organization_policy_assignment_id}	rms:organizationPolicyAssignments:delete	organizations:organizations:get
GET /v1/resource-manager/domains/{domain_id}/policy-assignments/{policy_assignment_id}/policy-states	rms:policyStates:get	-
GET /v1/resource-manager/domains/{domain_id}/policy-states	rms:policyStates:get	-
GET /v1/resource-manager/domains/{domain_id}/resources/{resource_id}/policy-states	rms:policyStates:get	-
POST /v1/resource-manager/domains/{domain_id}/policy-assignments/{policy_assignment_id}/policy-states/run-evaluation	rms:policyStates:runEvaluation	-
GET /v1/resource-manager/domains/{domain_id}/policy-assignments/{policy_assignment_id}/policy-states/evaluation-state	rms:policyStates:get	-
PUT /v1/resource-manager/domains/{domain_id}/policy-states	rms:policyStates:update	-
PUT /v1/resource-manager/domains/{domain_id}/aggregators	rms:aggregators:create	-
PUT /v1/resource-manager/domains/{domain_id}/aggregators/{aggregator_id}	rms:aggregators:update	-
DELETE /v1/resource-manager/domains/{domain_id}/aggregators/{aggregator_id}	rms:aggregators:delete	-
GET /v1/resource-manager/domains/{domain_id}/aggregators	rms:aggregators:list	-
GET /v1/resource-manager/domains/{domain_id}/aggregators/{aggregator_id}	rms:aggregators:get	-
GET /v1/resource-manager/domains/{domain_id}/aggregators/{aggregator_id}/aggregator-sources-status	rms:aggregators:get	-
POST /v1/resource-manager/domains/{domain_id}/aggregators/aggregate-data/policy-states/compliance-summary	rms:aggregatorResources:list	-
POST /v1/resource-manager/domains/{domain_id}/aggregators/aggregate-data/policy-assignments/compliance	rms:aggregatorResources:list	-
POST /v1/resource-manager/domains/{domain_id}/aggregators/aggregate-data/policy-states/compliance-details	rms:aggregatorResources:list	-
POST /v1/resource-manager/domains/{domain_id}/aggregators/aggregate-data/policy-assignment/detail	rms:aggregatorResources:list	-
POST /v1/resource-manager/domains/{domain_id}/aggregators/aggregate-resource-config	rms:aggregatorResources:get	-
POST /v1/resource-manager/domains/{domain_id}/aggregators/aggregate-data/aggregate-discovered-resources	rms:aggregatorResources:list	-
POST /v1/resource-manager/domains/{domain_id}/aggregators/{aggregator_id}/run-query	rms:aggregatorResources:runQuery	-
POST /v1/resource-manager/domains/{domain_id}/aggregators/aggregate-data/aggregate-discovered-resource-counts	rms:aggregatorResources:list	-
GET /v1/resource-manager/domains/{domain_id}/aggregators/aggregation-authorization	rms:aggregationAuthorizations:list	-
PUT /v1/resource-manager/domains/{domain_id}/aggregators/aggregation-authorization	rms:aggregationAuthorizations:create	-
DELETE /v1/resource-manager/domains/{domain_id}/aggregators/aggregation-authorization/{authorized_account_id}	rms:aggregationAuthorizations:delete	-
DELETE /v1/resource-manager/domains/{domain_id}/aggregators/pending-aggregation-request/{requester_account_id}	rms:aggregationRequests:delete	-
GET /v1/resource-manager/domains/{domain_id}/aggregators/pending-aggregation-request	rms:aggregationRequests:list	-
PUT /v1/resource-manager/domains/{domain_id}/tracker-config	rms:trackerConfig:put	-
DELETE /v1/resource-manager/domains/{domain_id}/tracker-config	rms:trackerConfig:delete	-
GET /v1/resource-manager/domains/{domain_id}/tracker-config	rms:trackerConfig:get	-
GET /v1/resource-manager/domains/{domain_id}/schemas	rms:schemas:list	-
GET /v1/resource-manager/policy-definitions	rms:policyDefinitions:get	-
GET /v1/resource-manager/policy-definitions/{policy_definition_id}	rms:policyDefinitions:get	-
GET /v1/resource-manager/domains/{domain_id}/resources/{resource_id}/history	rms:resources:getHistory	-
GET /v1/resource-manager/domains/{domain_id}/all-resources/{resource_id}/relations	rms:resources:getRelation	-
GET /v1/resource-manager/domains/{domain_id}/provider/{provider}/type/{type}/resources/{resource_id}	rms:resources:get	-
GET /v1/resource-manager/domains/{domain_id}/all-resources	rms:resources:list	-
GET /v1/resource-manager/domains/{domain_id}/provider/{provider}/type/{type}/resources	rms:resources:list	-
POST /v1/resource-manager/domains/{domain_id}/run-query	rms:resources:runQuery	-
GET /v1/resource-manager/domains/{domain_id}/all-resources/summary	rms:resources:list	-
GET /v1/resource-manager/domains/{domain_id}/all-resources/tags	rms:resources:list	-
GET /v1/resource-manager/domains/{domain_id}/all-resources/count	rms:resources:list	-
GET /v1/resource-manager/domains/{domain_id}/all-resources/{resource_id}	rms:resources:get	-
GET /v1/resource-manager/domains/{domain_id}/resources/{resource_id}/relations	rms:resources:summarize	-
GET /v1/resource-manager/domains/{domain_id}/tracked-resources	rms:resources:list	-
GET /v1/resource-manager/domains/{domain_id}/tracked-resources/count	rms:resources:list	-
GET /v1/resource-manager/domains/{domain_id}/tracked-resources/tags	rms:resources:list	-
GET /v1/resource-manager/domains/{domain_id}/tracked-resources/summary	rms:resources:list	-
GET /v1/resource-manager/domains/{domain_id}/tracked-resources/{resource_id}	rms:resources:get	-
POST /v1/resource-manager/{resource_type}/{resource_id}/tags/create	rms::tagResource	-
POST /v1/resource-manager/{resource_type}/{resource_id}/tags/delete	rms::unTagResource	-
GET /v1/resource-manager/{resource_type}/{resource_id}/tags	rms::listTagsForResource	-
GET /v1/resource-manager/{resource_type}/tags	rms::listTags	-
POST /v1/resource-manager/{resource_type}/resource-instances/count	rms::listResourcesByTag	-
POST /v1/resource-manager/{resource_type}/resource-instances/filter	rms::listResourcesByTag	-
PUT /v1/resource-manager/domains/{domain_id}/policy-assignments/{policy_assignment_id}/remediation-configuration	rms:policyAssignmentsRemediation:putRemediationConfiguration	iam:agencies:pass iam:agencies:createServiceLinkedAgencyV5
DELETE /v1/resource-manager/domains/{domain_id}/policy-assignments/{policy_assignment_id}/remediation-configuration	rms:policyAssignmentsRemediation:deleteRemediationConfiguration	-
GET /v1/resource-manager/domains/{domain_id}/policy-assignments/{policy_assignment_id}/remediation-configuration	rms:policyAssignmentsRemediation:getRemediationConfiguration	-
POST /v1/resource-manager/domains/{domain_id}/policy-assignments/{policy_assignment_id}/remediation-execution	rms:policyAssignmentsRemediation:runRemediation	functiongraph:function:invokeAsync functiongraph:function:getFunctionConfig rf:stack:create rf:stack:delete rf:stack:getTemplate rf:stack:getMetadata rf:privateTemplate:showMetadata
GET /v1/resource-manager/domains/{domain_id}/policy-assignments/{policy_assignment_id}/remediation-execution-statuses	rms:policyAssignmentsRemediation:listRemediationExecutionStatuses	-
POST /v1/resource-manager/domains/{domain_id}/policy-assignments/{policy_assignment_id}/remediation-execution-statuses/summary	rms:policyAssignmentsRemediation:listRemediationExecutionStatuses	-
POST /v1/resource-manager/domains/{domain_id}/policy-assignments/{policy_assignment_id}/remediation-exception/create	rms:policyAssignmentsRemediation:createRemediationExceptions	-
POST /v1/resource-manager/domains/{domain_id}/policy-assignments/{policy_assignment_id}/remediation-exception/delete	rms:policyAssignmentsRemediation:deleteRemediationExceptions	-
GET /v1/resource-manager/domains/{domain_id}/policy-assignments/{policy_assignment_id}/remediation-exception	rms:policyAssignmentsRemediation:listRemediationExceptions	-

Resources

A resource type indicates the resources that an SCP policy 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 Config.

**Table 3** Resource types supported by Config
Resource Type	URN
conformancePacks	rms::<account-id>:conformancePacks:<conformance-pack-id>
storedQueries	rms::<account-id>:storedQueries:<query-id>
policyAssignments	rms::<account-id>:policyAssignments:<policy-assignment-id>
organizationPolicyAssignments	rms::<account-id>:organizationPolicyAssignments:<organization-id>/<organization-policy-assignments-id>
organizationConformancePacks	rms::<account-id>:organizationConformancePacks:<organization-id>/<organization-conformance-pack-id>
aggregators	rms::<account-id>:aggregators:<aggregator-id>
aggregationAuthorizations	rms::<account-id>:aggregationAuthorizations:<authorized-account-id>
policyAssignmentsRemediation	rms::<account-id>:policyAssignmentsRemediation:<policy-assignment-id>

Conditions

A Condition element lets you specify conditions for when an SCP is in effect. It contains condition keys and operators.

A key in the Condition element of a statement Condition keys are classified into global condition keys and service-specific condition keys based on the application scope.
- Global condition keys (with the g: prefix) apply to all actions. Cloud services do not need to provide user identity information. Instead, the system automatically obtains such information and authenticates users. For details, see SCP Syntax.
- A service-specific condition key is prefixed by the service name (such as config:) and applies only to a specific service. For details, see Table 4.
- The number of values associated with a condition key in the request context of an API call makes the condition key single-valued or multivalued. Single-valued condition keys have at most one value in the request context of an API call. Multivalued condition keys can have multiple values in the request context of an API call. For example, a request can originate from at most one VPC endpoint, so g:SourceVpce is a single-valued condition key. You can tag resources and include multiple tag key-value pairs in a request, so g:TagKeys is a multivalued condition key.
An operator, a condition key, and a condition value constitute a complete condition statement. An SCP takes effect only when the statement meets related requirements. For supported condition operators, see SCP Syntax.

The following table lists the condition keys that you can define in SCPs for Config. You can include these condition keys to specify conditions for when your SCP is in effect.

**Table 4** Service-specific condition keys supported by Config
Condition Key	Type	Single-valued/Multivalued	Description
rms:AuthorizedAccountOrgPath	string	Single valued	Access control based on the Organizations Path of the specified aggregator account.
rms:TrackerBucketName	String	Single valued	Access control based on the specified bucket name.
rms:TrackerBucketPathPrefix	String	Single valued	Access control based on the specified folder of an OBS bucket.