Before You Start

Welcome to CodeArts Deploy. CodeArts Deploy provides visualized, one-click deployment. It supports deployment on VMs or containers by using Tomcat, Spring Boot, and other templates or by flexibly orchestrating atomic actions. It also supports parallel deployment and seamless integration with CodeArts Pipeline, providing standard deployment environments and implementing automatic deployment.

You can use the APIs described in this document to perform various operations, such as creating hosts and host clusters, and deploying applications. For details about all supported operations, see API Overview.

If you plan to access CodeArts Deploy through an API, ensure that you are familiar with CodeArts Deploy concepts. For details, see Service Overview.

Endpoints

An endpoint is the request address for calling an API. Endpoints vary depending on services and regions. You can query the endpoints of a service from "Regions and Endpoints".

Table 1 lists the endpoints of CodeArts Deploy. Select a desired one based on the service requirements.

**Table 1** CodeArts Deploy endpoints
Region Name	Region	Endpoint	Protocol
AP-Singapore	ap-southeast-3	codearts-deploy.ap-southeast-3.myhuaweicloud.com	HTTPS
LA-Mexico City2	la-north-2	codearts-deploy.la-north-2.myhuaweicloud.com codearts-deploy.la-north-2.myhuaweicloud.lat	HTTPS
LA-Sao Paulo1	sa-brazil-1	codearts-deploy.sa-brazil-1.myhuaweicloud.com codearts-deploy.sa-brazil-1.myhuaweicloud.lat	HTTPS

Glossary

Account
An account is created upon successful registration with Huawei 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 IAM users and grant them permissions for routine management.
User
A user is created using a domain to use cloud services. Each 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 from the dimensions of 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 the same 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)
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 support cross-AZ high-availability systems.
Project
Projects group and isolate resources (including compute, storage, network, and other resources) across 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. 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 isolation model

You can obtain the project ID on the My Credentials page.