Updated on 2026-11-20 GMT+08:00

Before You Start

Welcome to Application Operations Management (AOM) API Reference. AOM is a one-stop, multi-dimensional O&M management platform for cloud applications. It provides one-stop observability analysis and automated O&M. By collecting metrics, logs, and performance data from the cloud and local devices, AOM enables you to monitor real-time running status of applications, resources, and services and detect faults in a timely manner, improving O&M automation capability and efficiency.

This document describes how to use application programming interfaces (APIs) to perform operations on AOM, such as creation, deletion, and query. For details about all supported operations, see API Overview.

If you plan to call AOM APIs, ensure that you are familiar with AOM concepts. For details, see Service Overview.

Endpoints

An endpoint is the address used for calling an API. Endpoints vary by service and region. For the endpoints of all services, see Regions and Endpoints.

Concepts

  • Account

    When you sign up with the cloud, an account with full access to all of your cloud services and resources is created. It can be used to reset user passwords and grant user permissions. The account is the payer account, so it should not be used directly for routine management. To ensure account security, create IAM users and grant them the permissions required for such tasks.

  • IAM user

    IAM users are created by the account to use cloud services. Each IAM user has its own credentials (password or access keys).

    An IAM user can view the account ID and user ID on the My Credentials page of the console. The account name, username, and password will be required for API authentication.

  • Region

    Regions are defined by their geographical location and network latency. Public services, such as Elastic Cloud Server (ECS), Elastic Volume Service (EVS), Object Storage Service (OBS), Virtual Private Cloud (VPC), Elastic IP (EIP), and Image Management Service (IMS), are shared within a region. There are universal regions and dedicated regions. A universal region serves all tenants, while a dedicated region serves specific tenants.

    For details, see Region and AZ.

  • AZ

    An AZ contains one or more physical data centers. Each AZ has independent cooling, fire extinguishing, moisture control, and electrical facilities. Within an AZ, computing, network, storage, and other resources are logically divided into multiple clusters. AZs within a region are interconnected by optical fibers for high-availability networking.

  • Project

    Projects group and isolate resources (including compute, storage, and network resources) across physical regions. A default project is provided for each cloud region. Users can be granted permissions to access all resources in a specific project. For more refined access control, create subprojects under a project and purchase resources in the subprojects. Users can then be assigned permissions to access only specific resources in the subprojects.

    To view a project ID, go to the My Credentials page.

  • Enterprise project

    Enterprise projects group and manage resources across regions. Resources in enterprise projects are logically isolated. An enterprise project can contain resources in multiple regions, and resources can be directly transferred between enterprise projects.

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

API Calling

AOM supports Representational State Transfer (REST) APIs, allowing you to call APIs using HTTPS. For details about API calling, see Calling APIs.