EPS – Release of the Enterprise Project Management Service 

We are pleased to announce the availability of the new Enterprise Project Management Service (EPS) in the EU-DE and EU-NL regions.

The service enables centralized management of resources across multiple projects and supports the structured organization of cloud resources in larger environments.

EPS offers the following key features:

• Cross-region management of EPS projects
• Easy addition, deletion, or movement of resources within or between EPS projects
• Access control for project resources via IAM
• Centralized management of resources across multiple projects (e.g., management of KMS keys across authorized EPS projects)

A more detailed description of the service, a comparison with existing IAM projects, and a use case example can be found in the Community.

The full documentation is available in the Help Centers.

The service is free of charge.

• EPS is initially provided with a set of integrated services.
• Additional services will be integrated gradually over time.

The graphical user interface of integrated services (e.g., ECS, OBS, KMS, etc.) is updated:

• Existing resources will now display their associated project assignment.
• When creating new resources, a project must be selected.
• All existing resources are initially assigned to the “default” project.

For using EPS, it is recommended to create dedicated projects, add resources, and then grant the appropriate permissions to these projects.

With this release, new EPS APIs are being introduced.

• An API for project deletion will be added at a later stage.
• Until then, resources must either be moved or IAM permissions removed to revoke access.

Additionally, parameters for existing APIs of integrated services will become available.

• The API documentation for the integrated services will be updated over time to describe parameters for use with EPS (e.g., enterprise_project_id as a new optional parameter).

This release should not cause any conflicts with infrastructure-as-code applications such as Terraform. The parameter for assigning a resource to an EPS project is optional. If no project is specified, the resource will automatically be assigned to the “default” project.

After the project deletion API is made available, a Terraform provider for EPS will be developed and released.