Before You Start

Welcome to use Application Operations Management (AOM). 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 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 request address for calling an API. Endpoints vary depending on services and regions. For the endpoints of all services, see Regions and Endpoints.

Concepts

Account
An account is created upon successful registration with the cloud. The account 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 account is a payment entity and should not be used directly to perform routine management. For security purposes, create Identity and Access Management (IAM) users and grant them permissions for routine management.
IAM User
An IAM user is created using an account to use cloud services. Each IAM user has its own identity credentials (password and 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 divided by 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. Regions are classified into universal and dedicated regions. A universal region provides universal cloud services for common tenants. A dedicated region provides specific services for specific tenants.

For details, see Region and AZ.
Availability Zone (AZ)
AZs are physically isolated locations in a region, but are interconnected through an internal network for enhanced application availability.
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.

Figure 1 Project isolating model

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 transferred between enterprise projects.

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