Updated on 2026-02-13 GMT+08:00

Concepts

  • Account

    An account is created when registering with Huawei Cloud. An account has full access permissions to all the resources and cloud services under it, including resetting user passwords and granting user permissions. The account is a payment entity, which should not be used directly to perform routine management. To ensure account security, create IAM users and grant them permissions for routine management.

  • User

    A user is created by an account within IAM and represents a person using cloud services. Each user possesses credentials such as passwords and access keys.

    You can view the account ID and user ID on the My Credentials page of the console. The account, username, and password are required for API authentication.

  • Region

    Regions are divided based on geographical location and network latency. Within the same region, shared public services include Elastic Cloud Server (ECS), Elastic Volume Service (EVS), Object Storage Service (OBS), Virtual Private Cloud (VPC), Elastic IP (EIP), and Image Management Service (IMS). Regions are classified as universal regions and dedicated regions. A universal region provides universal cloud services for common tenants. A dedicated region provides services of the same type or only provides services for specific tenants.

  • AZ

    AZs are physically isolated locations in a region, but are interconnected through an internal network for enhanced application availability.

  • Project

    By default, each region in Huawei Cloud corresponds to a project pre-configured by the system. This project isolates resources (compute, storage, and network) between physical regions. A default project is provided for each region, and subprojects can be created under each default project. Users can be granted permissions to access all resources in a specific project. If finer-grained permission control is required, sub-projects can be created within the default project, and resources can be purchased within these sub-projects. Permissions can then be assigned at the sub-project level, enabling users to access only the resources within specific sub-projects, thereby providing more precise resource permission control.

    Figure 1 Project isolating model