Updated on 2025-11-06 GMT+08:00

Enterprise Center

IAM provides system-defined identity policies to define common actions supported by cloud services. You can also create custom identity policies using the actions supported by cloud services for more refined access control.

In addition to IAM policies, you can use service control policies (SCPs) provided by Organizations 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 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. The granted permissions can be applied only if they are allowed by the SCPs.

To learn more about how IAM policies are different from Organizations SCPs, see What Are the Differences Between IAM Policies and Organizations SCPs?

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

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 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 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 Enterprise Center, see Conditions.

  • The Alias column lists the policy actions that can be 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 Enterprise Center.

Table 1 Actions supported by Enterprise Center

Action

Description

Access Level

Resource Type (*: required)

Condition Key

Alias

businessUnitCenter::active

Grants permission to enable and disable Enterprise Center.

write

-

-

-

businessUnitCenter:bill:update

Grants permission to manage bills for enterprise members.

write

-

-

-

businessUnitCenter:bill:view

Grants permission to view bills of member accounts.

read

-

-

-

businessUnitCenter:billDetail:update

Grants permission to perform operations on bill details for enterprise members.

write

-

-

-

businessUnitCenter:billDetail:view

Grants permission to view bill details of member accounts.

read

-

-

-

businessUnitCenter:businessUnitFinance:update

Grants permission to modify organization accounting information.

write

-

-

-

businessUnitCenter:businessUnitFinance:view

Grants permission to view organization accounting information.

read

-

-

-

businessUnitCenter:businessUnit:update

Grants permission to modify organizations and accounts

write

-

-

-

businessUnitCenter:businessUnit:view

Grants permission to view organizations and accounts

read

-

-

-

businessUnitCenter:businessUnitBudget:update

Grants permission to update organization budgets

write

-

-

-

businessUnitCenter:businessUnitBudget:view

Grants permission to view organization budgets

read

-

-

-

businessUnitCenter:businessUnitPolicy:update

Grants permission to modify organization policies.

write

-

-

-

For details about the relationship between Enterprise Center APIs and actions, see Customer Operations.

Resource Type (*: required)

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

Conditions

Enterprise Center 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.