Help Center/ Resource Governance Center/ API Reference/ Permissions and Supported Actions/ Actions Supported by Policy-based Authorization
Updated on 2025-02-20 GMT+08:00

Actions Supported by Policy-based Authorization

IAM provides system-defined policies to define common actions supported by cloud services. You can also create custom 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.

The organization's management account can use SCPs to ensure your member accounts stay within your organization's access and control guidelines. They can be attached to an organization, OUs, or member accounts. Any SCP attached to an organization or OU affects all the accounts within the organization or under the OU. The granted permissions can be applied only if they are allowed by the SCPs.

This section describes the elements used by IAM custom policies and Organizations SCPs. The elements include actions, resources, and conditions.

Actions

Actions are specific operations that are allowed or denied in a policy.

  • 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 a 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 policy 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.
  • The Condition Key column includes keys that you can specify in the Condition element of a 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.

The following table lists the actions that you can define in custom policies 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-compliance.

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 enabled governance policies.

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 preset 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/managed-organizational/organizational-unit/{organizational_unit_id}/register

rgc:organizationalUnit:register

-

GET /v1/managed-organizational/{operation_id}

rgc:operation:get

-

GET /v1/managed-organizational/managed-account/{managed_account_id}

rgc:managedAccount:get

-

POST /v1/managed-organizational/managed-accounts

rgc:account:create

-

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/enabled-controls

rgc:enabledControls:list

-

GET /v1/governance/managed-organizational-unit/{managed_organizational_unit_id}/controls

rgc:controlsForOrganizationalUnit:list

-

Resources

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

Conditions

RGC does not support service-specific condition keys in policies.

It can only use global condition keys applicable to all services. For details, see Global Condition Keys.