Help Center/ Enterprise Management/ API Reference (Ankara Region)/ Before You Start
Updated on 2025-03-31 GMT+08:00
View PDF
Share

Before You Start

Welcome to Enterprise Project Management Service (EPS). EPS allows you to manage resources and personnel by enterprise project.

This document describes how to use application programming interfaces (APIs) to perform operations on enterprise projects, such as querying, creating, and modifying enterprise projects. For details about all supported operations, see API Overview.

Before using EPS APIs, ensure that you are familiar with EPS concepts. For details, see Enterprise Management User Guide.

EPS supports REST APIs, allowing you to call APIs using HTTPS. For details about API calling, see API Calling.

Resources Supported by EPS

You can obtain the cloud services and resources supported by EPS by calling the API for querying services supported by EPS. The provider field indicates the cloud service name, and the resource_type field indicates the resource type.

Endpoints

An endpoint is the request address for calling an API. Endpoints vary depending on services and regions. To obtain the regions and endpoints, contact the enterprise administrator.

Concepts

  • Account

    A domain has full access permissions for all of its cloud services and resources. It can be used to reset user passwords and grant user permissions. The domain should not be used directly to perform routine management. To ensure domain security, create Identity and Access Management (IAM) users and grant them permissions for routine management.

  • User

    An IAM user is created by an account in IAM to use cloud services. Each IAM user has its own identity credentials (password and access keys).

    API authentication requires information such as the domain name, username, and password.

  • Region

    A region is a geographic area in which cloud resources are deployed. Availability zones (AZs) in the same region can communicate with each other over an intranet, while AZs in different regions are isolated from each other. Deploying cloud resources in different regions can better suit certain user requirements or comply with local laws or regulations.

  • AZ

    An AZ comprises of one or more physical data centers equipped with independent ventilation, fire, water, and electricity facilities. Computing, network, storage, and other resources in an AZ are logically divided into multiple clusters. AZs within a region are interconnected using high-speed optical fibers to allow you to build cross-AZ high-availability systems.

  • Project

    A project corresponds to a region. Default projects are defined to group and physically isolate resources (including compute, storage, and network resources) across regions. Users can be granted permissions in a default project to access all resources under their domains in the region associated with the project. If you need more refined access control, create subprojects under a default project and add resources to subprojects. Then you can assign users the permissions required to access only the resources in the specific subprojects.

    Figure 1 Project isolating model
  • Enterprise Project

    Enterprise projects group and manage resources across regions. Resources in different enterprise projects are logically isolated. An enterprise project can contain resources of multiple regions, and resources can be added to or removed from enterprise projects.

    For details about enterprise projects and about how to obtain enterprise project IDs, see Enterprise Management User Guide.