Resource Governance Center (RGC)

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 RGC, 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 RGC, 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 RGC.

**Table 1** Actions supported by RGC
Action	Description	Access Level	Resource Type (*: required)	Condition Key	Alias
rgc:control:list	Grants permission to list governance policies.	List	-	-	-
rgc:controlViolation:list	Grants permission to list non-compliant resources.	List	-	-	-
rgc:control:get	Grants permission to get the 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 identify the enabling status of a governance policy.	Read	-	-	-
rgc:enabledControl:list	Grants permission to list governance policies enabled for an organization.	List	-	-	-
rgc:controlsForOrganizationalUnit:list	Grants permission to list governance policies enabled for an organizational unit.	List	-	-	-
rgc:controlsForAccount:list	Grants permission to list governance policies enabled for an account.	List	-	-	-
rgc:complianceStatusForAccount:get	Grants permission to identify the compliance status of resources in a managed account in an organization.	Read	-	-	-
rgc:complianceStatusForOrganizationalUnit:get	Grants permission to identify the compliance status of resources in all managed accounts in a registered organizational unit in an organization.	Read	-	-	-
rgc:controlsForOrganizationalUnit:get	Grants permission to get the details about governance policies enabled for a registered organizational unit in an organization.	Read	-	-	-
rgc:controlsForAccount:get	Grants permission to get the details about governance policies enabled for a managed account in an organization.	Read	-	-	-
rgc:configRuleCompliance:list	Grants permission to list managed accounts for compliance against Config rules.	List	-	-	-
rgc:externalConfigRuleCompliance:list	Grants permission to list managed accounts for compliance against external Config rules.	List	-	-	-
rgc:driftDetail:list	Grants permission to list the drift summary of the landing zone.	List	-	-	-
rgc:managedOrganizationalUnit:register	Grants permission to register an organizational unit.	Write	-	-	-
rgc:managedOrganizationalUnit:reRegister	Grants permission to re-register an organizational unit.	Write	-	-	-
rgc:managedOrganizationalUnit:deRegister	Grants permission to deregister an organizational unit.	Write	-	-	-
rgc:operation:get	Grants permission to get the details about registration, re-registration, or deregistration of an organizational unit.	Read	-	-	-
rgc:managedOrganizationalUnit:delete	Grants permission to delete an organizational unit.	Write	-	-	-
rgc:managedOrganizationalUnit:get	Grants permission to get the details about a registered organizational unit.	Read	-	-	-
rgc:managedOrganizationalUnit:create	Grants permission to create an organizational unit.	Write	-	-	-
rgc:managedOrganizationalUnit:list	Grants permission to list registered organizational units that governance policies have been enabled for.	List	-	-	-
rgc:managedAccount:enroll	Grants permission to manage an account.	Write	-	-	-
rgc:managedAccount:unEnroll	Grants permission to unmanage an account.	Write	-	-	-
rgc:managedAccount:update	Grants permission to update a managed account.	Write	-	-	-
rgc:managedAccount:get	Grants permission to get the details about a managed account.	Read	-	-	-
rgc:managedAccountsForParent:list	Grants permission to list managed accounts in a registered organizational unit.	List	-	-	-
rgc:managedAccount:create	Grants permission to create an account.	Write	-	-	-
rgc:managedAccount:list	Grants permission to list managed accounts that governance policies have been enabled for.	List	-	-	-
rgc:managedCoreAccount:get	Grants permission to get the details about a managed core account.	Read	-	-	-
rgc:homeRegion:get	Grants permission to get the details about the home region of the landing zone.	Read	-	-	-
rgc:preLaunch:check	Grants permission to check whether the current region is eligible for setting up a landing zone.	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 identify the status of landing zone setup.	Read	-	-	-
rgc:availableUpdate:get	Grants permission to identify the available updates of a landing zone.	Read	-	-	-
rgc:landingZoneConfiguration:get	Grants permission to get the configurations of a landing zone.	Read	-	-	-
rgc:landingZoneIdentityCenter:get	Grants permission to get the details about IAM Identity Center users of a landing zone.	Read	-	-	-
rgc:operation:list	Grants permission to obtain the current operation status of a registered OU or a managed account.	List	-	-	-
rgc:templateDeployParam:get	Grants permission to show the deploy parameters of the template.	Read	-	-	-
rgc:template:create	Grants permission to create template.	Write	-	-	-
rgc:template:delete	Grants permission to delete template.	Write	-	-	-
rgc:predefinedTemplate:list	Grants permission to list the predefined templates.	List	-	-	-
rgc:managedAccountTemplate:get	Grants permission to get the template details about a managed account.	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
GET /v1/governance/controls	rgc:control:list	-
GET /v1/governance/control-violations	rgc:controlViolation:list	-
GET /v1/governance/controls/{control_id}	rgc:control:get	-
POST /v1/governance/controls/enable	rgc:control:enable	-
POST /v1/governance/controls/disable	rgc:control:disable	-
GET /v1/governance/operation-control-status/{operation_control_status_id}	rgc:controlOperate:get	-
GET /v1/governance/enabled-controls	rgc:enabledControl:list	-
GET /v1/governance/managed-organizational-units/{managed_organizational_unit_id}/controls	rgc:controlsForOrganizationalUnit:list	-
GET /v1/governance/managed-accounts/{managed_account_id}/controls	rgc:controlsForAccount:list	-
GET /v1/governance/managed-accounts/{managed_account_id}/compliance-status	rgc:complianceStatusForAccount:get	-
GET /v1/governance/managed-organizational-units/{managed_organizational_unit_id}/compliance-status	rgc:complianceStatusForOrganizationalUnit:get	-
GET /v1/governance/managed-organizational-units/{managed_organizational_unit_id}/controls/{control_id}	rgc:controlsForOrganizationalUnit:get	-
GET /v1/governance/managed-accounts/{managed_account_id}/controls/{control_id}	rgc:controlsForAccount:get	-
GET /v1/governance/managed-accounts/{managed_account_id}/config-rule-compliances	rgc:configRuleCompliance:list	-
GET /v1/governance/managed-accounts/{managed_account_id}/external-config-rule-compliances	rgc:externalConfigRuleCompliance:list	-
GET /v1/governance/drift-details	rgc:driftDetail:list	-
POST /v1/managed-organization/organizational-units/{organizational_unit_id}/register	rgc:managedOrganizationalUnit:register	-
POST /v1/managed-organization/organizational-units/{organizational_unit_id}/re-register	rgc:managedOrganizationalUnit:reRegister	-
POST /v1/managed-organization/managed-organizational-units/{managed_organizational_unit_id}/de-register	rgc:managedOrganizationalUnit:deRegister	-
GET /v1/managed-organization/{operation_id}	rgc:operation:get	-
DELETE /v1/managed-organization/managed-organizational-units/{managed_organizational_unit_id}	rgc:managedOrganizationalUnit:delete	-
GET /v1/managed-organization/managed-organizational-units/{managed_organizational_unit_id}	rgc:managedOrganizationalUnit:get	-
POST /v1/managed-organization/managed-organizational-units	rgc:managedOrganizationalUnit:create	-
GET /v1/managed-organization/managed-organizational-units	rgc:managedOrganizationalUnit:list	-
POST /v1/managed-organization/accounts/{managed_account_id}/enroll	rgc:managedAccount:enroll	-
POST /v1/managed-organization/managed-accounts/{managed_account_id}/un-enroll	rgc:managedAccount:unEnroll	-
POST /v1/managed-organization/managed-accounts/{managed_account_id}/update	rgc:managedAccount:update	-
GET /v1/managed-organization/managed-accounts/{managed_account_id}	rgc:managedAccount:get	-
GET /v1/managed-organization/managed-organizational-units/{managed_organizational_unit_id}/managed-accounts	rgc:managedAccountsForParent:list	-
POST /v1/managed-organization/managed-accounts	rgc:managedAccount:create	-
GET /v1/managed-organization/managed-accounts	rgc:managedAccount:list	-
GET /v1/managed-organization/managed-core-accounts	rgc:managedCoreAccount:get	-
GET /v1/landing-zone/home-region	rgc:homeRegion:get	-
POST /v1/landing-zone/pre-launch-check	rgc:preLaunch:check	-
POST /v1/landing-zone/setup	rgc:landingZone:setup	-
POST /v1/landing-zone/delete	rgc:landingZone:delete	-
GET /v1/landing-zone/status	rgc:landingZoneStatus:get	-
GET /v1/landing-zone/available-updates	rgc:availableUpdate:get	-
GET /v1/landing-zone/configuration	rgc:landingZoneConfiguration:get	-
GET /v1/landing-zone/identity-center	rgc:landingZoneIdentityCenter:get	-
GET /v1/managed-organization	rgc:operation:list	-
GET /v1/rgc/templates/{template_name}/deploy-params	rgc:templateDeployParam:get	-
POST /v1/rgc/templates	rgc:template:create	-
DELETE /v1/rgc/templates/{template_name}	rgc:template:delete	-
GET /v1/rgc/predefined-templates	rgc:predefinedTemplate:list	-
GET /v1/managed-organization/managed-accounts/{managed_account_id}/blueprint	rgc:managedAccountTemplate:get	-

Resources

RGC does not support resource-level authorization. To allow access to RGC, use a wildcard (*) in the Resource element of the identity policy, indicating that the identity policy will be applied to all resources.

Conditions

RGC 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: Management & Governance

Previous topic: IAM Access Analyzer (IAA)

Next topic: Cloud Operations Center (COC)