Resource Governance Center (RGC)

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 IAM custom identity policies and 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 (such as 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 RGC, see Resources.
The Condition Key column includes 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 RGC, see Conditions.

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

**Table 1** Actions supported by RGC
Action	Description	Access Level	Resource Type (*: required)	Condition Key
rgc:control:list	Grants permission to list all governance policies.	list	-	-
rgc:controlViolation:list	Grants permission to list non-compliant governance policies.	list	-	-
rgc:control:get	Grants permission to get details about a governance policy.	read	-	-
rgc:control:enable	Grants permission to enable a governance policy.	write	-	-
rgc:control:disable	Grants permission to disable a governance policy.	write	-	-
rgc:controlOperate:get	Grants permission to query the status of a governance policy.	read	-	-
rgc:enabledControl:list	Grants permission to list governance policies that are enabled.	list	-	-
rgc:controlsForOrganizationalUnit:list	Grants permission to list governance policies enabled for a registered OU.	list	-	-
rgc:controlsForAccount:list	Grants permission to list governance policies enabled for an enrolled account.	list	-	-
rgc:complianceStatusForAccount:get	Grants permission to query the resource compliance status of an enrolled account in an organization.	read	-	-
rgc:complianceStatusForOrganizationalUnit:get	Grants permission to query the resource compliance status of all enrolled accounts under a registered OU in an organization.	read	-	-
rgc:controlsForOrganizationalUnit:get	Grants permission to list governance policies enabled for an OU.	read	-	-
rgc:controlsForAccount:get	Grants permission to list governance policies enabled for an account.	read	-	-
rgc:configRuleCompliance:list	Grants permission to query the Config rule compliance for enrolled accounts.	list	-	-
rgc:externalConfigRuleCompliance:list	Grants permission to list the external Config rule compliance for enrolled accounts.	list	-	-
rgc:driftDetail:list	Grants permission to query drift details.	list	-	-
rgc:managedOrganizationalUnit:register	Grants permission to register an OU.	write	-	-
rgc:managedOrganizationalUnit:reRegister	Grants permission to re-register an OU.	write	-	-
rgc:managedOrganizationalUnit:deRegister	Grants permission to deregister an OU.	write	-	-
rgc:operation:get	Grants permission to obtain registration information.	read	-	-
rgc:managedOrganizationalUnit:delete	Grants permission to delete a registered OU.	write	-	-
rgc:managedOrganizationalUnit:get	Grants permission to get details of a registered OU.	read	-	-
rgc:managedOrganizationalUnit:create	Grants permission to create an OU.	write	-	-
rgc:managedOrganizationalUnit:list	Grants permission to list registered OUs for which governance policies are enabled.	list	-	-
rgc:managedAccount:enroll	Grants permission to enroll an account.	write	-	-
rgc:managedAccount:unEnroll	Grants permission to unmanage an account.	write	-	-
rgc:managedAccount:update	Grants permission to update an enrolled account.	write	-	-
rgc:managedAccount:get	Grants permission to get details of an enrolled account.	read	-	-
rgc:managedAccountsForParent:list	Grants permission to list all enrolled accounts in a registered OU.	list	-	-
rgc:managedAccount:create	Grants permission to create an account.	write	-	-
rgc:managedAccount:list	Grants permission to list enrolled accounts for which governance policies are enabled.	list	-	-
rgc:managedCoreAccount:get	Grants permission to get details of an enrolled core account.	read	-	-
rgc:homeRegion:get	Grants permission to identify the home region.	read	-	-
rgc:preLaunch:check	Grants permission to perform pre-checks before landing zone setup.	write	-	-
rgc:landingZone:setup	Grants permission to set up a landing zone.	write	-	-
rgc:landingZone:delete	Grants permission to delete a landing zone.	write	-	-
rgc:landingZoneStatus:get	Grants permission to query the landing zone setup status.	read	-	-
rgc:availableUpdate:get	Grants permission to query the updateable status of a landing zone.	read	-	-
rgc:landingZoneConfiguration:get	Grants permission to query landing zone settings.	read	-	-
rgc:landingZoneIdentityCenter:get	Grants permission to obtain IAM Identity Center user information.	read	-	-
rgc:operation:list	Grants permission to query the status of a registered OU or an enrolled account.	list	-	-
rgc:templateDeployParam:get	Grants permission to obtain template deployment parameters.	read	-	-
rgc:template:create	Grants permission to create a template.	write	-	-
rgc:template:delete	Grants permission to delete a template.	write	-	-
rgc:predefinedTemplate:list	Grants permission to list preconfigured templates.	list	-	-
rgc:managedAccountTemplate:get	Grants permission to get details of a template for enrolled accounts.	read	-	-

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

**Table 2** Actions and dependencies supported by RGC APIs
API	Action	Dependencies
POST /v1/governance/control/enable	rgc:control:enable	-
POST /v1/governance/control/disable	rgc:control:disable	-
GET /v1/governance/operated-controls/{control_operate_request_id}	rgc:controlOperate:get	-
GET /v1/governance/managed-organizational-unit/{managed_organizational_unit_id}/controls	rgc:controlsForOrganizationalUnit:list	-

Resources

RGC does not support resource-specific permission control in SCPs. If you want to allow access to RGC, use the wildcard (*) for the Resource element to apply SCPs to all resources.