Enterprise Project Management Service (EPS)

Organizations provides your with Service Control Policies 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 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.

This section describes the elements used by 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 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 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 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 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 this column is empty (-), the action does not support any condition keys.
For details about the condition keys defined by EPS, see Conditions.

The following table lists the actions that you can define in custom policies for EPS.

**Table 1** Supported actions
Action	Description	Access Level	Resource Type (*: Required)	Condition Key
eps:enterpriseProjects:list	Grants permission to list enterprise projects.	list	enterpriseProject *	-
eps:enterpriseProjects:create	Grants permission to create enterprise projects.	write	enterpriseProject *	-
eps:enterpriseProjects:update	Grants permission to modify enterprise projects.	write	enterpriseProject *	-
eps:enterpriseProjects:enable	Grants permission to enable enterprise projects.	write	enterpriseProject *	-
eps:enterpriseProjects:disable	Grants permission to disable enterprise projects.	write	enterpriseProject *	-
eps:resources:list	Grants permission to list resources in an enterprise project.	list	enterpriseProject *	-
eps:resources:add	Grants permission to add resources to an enterprise project.	write	enterpriseProject *	-
eps:resources:remove	Grants permission to remove resources from an enterprise project.	write	enterpriseProject *	-

An EPS API usually supports one or more actions. Table 2 lists actions supported by each API and dependencies of actions.

**Table 2** Actions and dependencies
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 /v1.0/enterprise-projects/{enterprise_project_id}/action	eps:enterpriseProjects:disable	-
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
POST /v1.0/enterprise-projects/{enterprise_project_id}/resources-migrate	eps:resources:remove	eps:resources:add

Resources

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

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