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

Enterprise Project Management Service (EPS)

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

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

Table 1 Actions supported by EPS

Action

Description

Access Level

Resource Type (*: required)

Condition Key

Alias

eps:enterpriseProjects:list

Grants permission to view the enterprise project list.

List

enterpriseProject *

-

-

eps:enterpriseProjects:create

Grants permission to create an enterprise project.

Write

enterpriseProject *

-

-

eps:enterpriseProjects:update

Grants permission to modify an enterprise project.

Write

enterpriseProject *

-

-

eps:enterpriseProjects:enable

Grants permission to enable an enterprise project.

Write

enterpriseProject *

-

-

eps:enterpriseProjects:disable

Grants permission to disable an enterprise project.

Write

enterpriseProject *

-

-

eps:enterpriseProjects:delete

Grants permission to delete an enterprise project.

Write

enterpriseProject *

-

-

eps:resources:list

Grants permission to view resources in an enterprise project.

List

enterpriseProject *

-

-

eps:resources:add

Grants permission to add resources to an enterprise project.

Write

enterpriseProject *

-

-

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

Table 2 Actions and dependencies supported by EPS APIs

API

Action

Dependencies

GET /v1.0/enterprise-projects

eps:enterpriseProjects:list

-

POST /v1.0/enterprise-projects

eps:enterpriseProjects:create

-

PUT /v1.0/enterprise-projects/{enterprise_project_id}

eps:enterpriseProjects:update

-

POST /v1.0/enterprise-projects/{enterprise_project_id}/action

eps:enterpriseProjects:enable

-

POST 01 /v1.0/enterprise-projects/{enterprise_project_id}/action

eps:enterpriseProjects:disable

-

DELETE /v1.0/enterprise-projects/{enterprise_project_id}

eps:enterpriseProjects:delete

-

POST /v1.0/enterprise-projects/{enterprise_project_id}/resources/filter

eps:resources:list

-

POST /v1.0/enterprise-projects/{enterprise_project_id}/resources-migrate

eps:resources:add

eps:resources:remove

Resources

A resource type indicates the resources that an identity policy applies to. If you specify a resource type for any action in Table 3, the resource URN must be specified in the identity policy statements using that action, and the identity policy applies only to resources of this type. If no resource type is specified, the Resource element is marked with an asterisk (*) and the identity policy applies to all resources. You can also set condition keys in an identity policy to define resource types.

The following table lists the resource types that you can define in identity policy statements for EPS.

Table 3 Resource types supported by EPS

Resource Type

URN

enterpriseProject

eps::<account-id>:enterpriseProject:<enterprise-project-id>

Conditions

EPS 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.