Before You Start

Huawei Cloud Astro Zero is a no-/low-code development platform. It is built on Huawei practices in application development and digital transformation to improve development efficiency. Astro Zero also provides application asset development standards and microservice frameworks, helping enterprises accumulate replicable suites, accelerate application customization, and monetize suites through an open ecosystem. On this platform, you can use its visual orchestration tools, such as GUIs, logic, and objects, to quickly build applications through drag-and-drop operations.

This document describes how to use application programming interfaces (APIs) to perform operations on data, metadata, access control, scripts, and flows on Huawei Cloud Astro Zero, such as running, terminating, or deleting a flow instance. For details about supported operations, see API Overview.

Endpoints

An endpoint is the request address for calling an API. The default develop-state domain name of a Huawei Cloud Astro Zero endpoint is appcube.cn-north-4.huaweicloud.com.

appcube.cn-north-4.huaweicloud.com is used as an example domain name of the development environment in this document. The actual domain name is subject to your region.

Concepts

Account
An account is created upon successful registration. 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 IAM users and grant them permissions for routine management.
User
An Identity and Access Management (IAM) user is created using an account to use cloud services. Each IAM user has its own identity credentials (password and access keys).

In Huawei Cloud Astro Zero, users can develop applications, manage and configure applications, and manage portal users.
Portal User
Portal users access the applications developed in Huawei Cloud Astro Zero. For example, a device maintenance management service application is developed by user A. The customer service personnel, dispatchers, and maintenance personnel who use this service application are portal users. User A is a user but not a portal user.
Region
Regions are geographic areas isolated from each other. Resources are region-specific and cannot be used across regions through internal network connections. For low network latency and quick resource access, select the nearest region. The choice of regions may also be subject to legal compliance requirements.

For the regions of all services, see Region and AZ.
Availability Zone (AZ)
An availability zone (AZ) contains one or more physical data centers. Each AZ has independent cooling, fire extinguishing, moisture-proof, and electricity facilities. Within an AZ, computing, network, storage, and other resources 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. Projects are preset by the system and have physically isolated resources (including compute, storage, and network resources) across regions. Users can be granted permissions in a default project to access all resources in the region associated with the project. For more refined access control, create subprojects under a project and create resources in the subprojects. Users can then be assigned permissions to access only specific resources in the subprojects.

Figure 1 Project isolating model
Enterprise Project
Enterprise projects group and manage resources across regions. Resources in enterprise projects are logically isolated from each other. An enterprise project can contain resources in multiple regions, and resources can be transferred between enterprise projects.