Resource Indexes
Service |
Element |
Description |
---|---|---|
Traffic Cleansing |
The AntiDDos.Service element is a traffic cleaning service that can prevent DDoS attacks against Elastic IP Address (EIP). |
|
Application Orchestration Service (AOS) |
The AOS.Batch element is a batch processing object. It is used to create and deploy jobs in batches. By defining contained sub-objects and the number of batch processing times, the AOS.Batch element implements the batch processing function. The AOS.Batch element considers that the execution succeeds only after all the batch operations of the included objects are complete. Currently, the AOS.Batch element supports the following sub-objects: CCE.Job, CCE.Deployment, and AOS.Stack. |
|
The AOS.Stack element is a Huawei PaaS solution deployment template. It is used to create stack resources of AOS so that AOS can orchestrate various resources. The AOS.Stack element corresponds to the solution in real scenarios. It can implement one-click deployment of the solution. After being defined, the element can be replicated in batches, helping services to be quickly deployed on the cloud. |
||
API Gateway |
API providers configure APIs in API gateways to open backend capabilities. An API is divided into two parts. The first part is oriented to API users and defines how to invoke the API. The second part is oriented to API providers and defines the backend status of the API and how to access backend services through an API gateway. |
|
An API group is an API management unit. An API group is equivalent to a service entry. When an API group is created, a subdomain name is returned as the access entry. |
||
The request throttling function allows you to limit the number of API calls within a specified period to protect backend services. After APIs go online, the system provides an access control policy for each API by default. API providers can change the access control policy based on the service capabilities and load conditions of their APIs. |
||
Application Performance Management (APM) |
The APM.AutoScaler element is used to control elastic scaling of applications. |
|
The APM.Pinpoint element is used to orchestrate a stack containing the Pinpoint monitoring policy. After the stack is successfully deployed, you can view the monitoring group and monitoring details of the applications in the stack on the monitoring page. |
||
Cloud Container Engine (CCE) |
CCE.Addon.AutoScaler is a plug-in for node auto-scaling in a Kubernetes cluster. |
|
The CCE.Cluster element is used to deploy Kubernetes cluster resources at the Huawei PaaS layer. A master node can be created based on this element to manage and create slave nodes. This element provides the application orchestration function for users. |
||
The CCE.ConfigMap is used to provide basic configuration information storage services for the cluster creation of Huawei CCE. Sensitive information is prohibited in ConfigMap. |
||
The CCE.DaemonSet element is used to create a DaemonSet object in the Kubernetes cluster. Currently, the Kubernetes native YAML file can be used to create the object. |
||
The CCE.Deployment element is used to create a Deployment object in the Kubernetes cluster on Huawei CCE. Currently, the Kubernetes native YAML file can be used to create the object. |
||
Helm is a type of Kubernetes-based package specifications provided by CCE. The CCE.HelmRelease element is a deployment instance of the Helm package. |
||
The CCE.Ingress element is used to create an Ingress object in the Kubernetes cluster on CCE. Currently, the Kubernetes native YAML file can be directly used to create such an object. |
||
The CCE.Job element is used to create a Job object in the Kubernetes cluster on Huawei CCE. |
||
The CCE.NodePool element is used to deploy Kubernetes node resources at the Huawei PaaS layer. Deploying this type of resources enables users to orchestrate Huawei cloud resources on nodes, providing more powerful functions. |
||
The CCE.Pod element is used to create a pod in the Kubernetes cluster on the CCE. |
||
The CCE.Secret element is used to provide encryption information storage services for the cluster creation of Huawei CCE. The Secret object can contain sensitive configuration information such as usernames, passwords, and certificates. |
||
The CCE.Service element is used to deploy a Kubernetes resource object Service at the PaaS layer of HUAWEI CLOUD. By creating such an object, you can provide a unified entry address for a group of containerized applications with the same functions, and distribute requests in load balancing mode to backend containerized applications. |
||
The CCE.StatefulSet element is used to create a StatefulSet on a CCE cluster. |
||
The CCE.Storage.EVS element corresponds to an Elastic Volume Service (EVS) disk under CCE storage management. This type of resources must be used together with CCE clusters. |
||
The CCE.Storage.OBS element corresponds to object storage volumes in the CCE storage management function. This type of resources must be used together with CCE clusters. |
||
The CCE.Storage.SFS element corresponds to file storage volumes in the CCE storage management function. This type of resources must be used together with CCE clusters. |
||
Cloud Container Instance (CCI) |
The CCI.ConfigMap element is used to create a configMap. |
|
The CCI.Deployment element is used to create a deployment. |
||
The CCI.Ingress element is used to create an ingress. |
||
The CCI.Job element is used to create a job. |
||
The CCI.Namespace element is used to create a namespace. |
||
The CCI.Secret element is used to create a secret. In Kubernetes, secrets are used to carry sensitive information. |
||
The CCI.Service element is used to create a service. |
||
The CCI.StatefulSet element is used to create a StatefulSet. |
||
The CCI.Storage.EVS element is used to create a Persistent Volume Claim (PVC) under a specified namespace. |
||
The CCI.Storage.SFS element is used to create an SFS file system under a specified namespace. |
||
Content Delivery Network (CDN) |
The CDN.Cache element is used to set cache policies for resources on CDN nodes. |
|
The CDN.Domain element indicates the acceleration domain name. |
||
The CDN.Host element can be used to modify the retrieval host. The retrieval host information indicates the host information contained in an HTTP request header. A retrieval host is the site domain name accessed by CDN nodes during retrieval. |
||
The CDN.Https element can be used to configure the HTTPS of the acceleration domain name. You can configure the HTTPS certificate of the acceleration domain name and deploy it on network-wide CDN nodes to implement secure acceleration. |
||
The CDN.PreheatJob element can be used to create a preheating job. |
||
The CDN.Referer element is used to configure referer filtering rules. You can set referer filtering policies to identify and filter users, controlling access. |
||
The CDN.RefreshJob element can be used to create a cache refreshing job. |
||
The CDN.Source element can be used to modify information about the source server. Both the IP address and domain name of the source server can direct CDN nodes back to the source server. A source domain name cannot be the same as an acceleration domain name. |
||
Database Security Service (DBSS) |
The DBSS.Instance element is used to create Database Security Service (DBSS) resources. |
|
Distributed Cache Service (DCS) |
Distributed Cache Service (DCS) provides online distributed cache capabilities that are ready to use out of the box, secure, reliable, scalable, and easy to manage. It is compatible with Redis and Memcached and provides various instance types such as single-node, active/standby, and cluster, meeting users' requirements for high concurrency and fast data access. |
|
Document Database Service (DDS) |
The DDS.CommunityReplicaSetOrSingle element is used to create a replica set instance or a single-node instance. |
|
Data Ingestion Service (DIS) |
The DIS.Stream element is used to create cloud channel resources. You can use these resources to improve collection, transmission, and distribution capabilities. |
|
Elastic Cloud Server (ECS) |
The ECS.CloudServer element is used to deploy the ECS at Huawei cloud IaaS layer. It consists of CPUs, memory, images, and EVS disks. |
|
An ECS group allows you to create ECSs on different hosts, thereby improving service reliability. This function does not apply to existing ECSs. You cannot add existing ECSs to an ECS group. |
||
ECS.KeyPair is used to create a key pair for remote login authentication. To ensure security, you are advised to use the key authentication mode when logging in to an ECS. |
||
Elastic Volume Service (EVS) |
EVS.NonSharedVolume is used to deploy non-shared Elastic Volume Service (EVS) disks at the IaaS layer of HUAWEI CLOUD. Such disks provide scalable block storage that features high reliability, high performance, and rich specifications for servers. |
|
The EVS.SharedVolume element is used to deploy shared EVS disks at the IaaS layer. Shared EVS disks are block storage devices that can be attached to multiple ECSs and support concurrent read/write operations. These disks feature multiple attachments, high-concurrency, high-performance, and high-reliability. |
||
FunctionGraph Service (FGS) |
FGS.ApigEventMap is used to create APIG trigger resources for FunctionGraph. APIG triggers depend on the API Gateway service. Based on APIG trigger events, APIG triggers can trigger function execution. |
|
The FGS.CtsEventMap element is used to create Cloud Trace Service (CTS) trigger resources for FunctionGraph. CTS triggers depend on the CTS service. To create CTS triggers, you need to enable the CTS service first. Based on CTS events, CTS triggers can trigger function execution. |
||
The FGS.DisEventMap element is used to create Data Ingestion Service (DIS) trigger resources for FunctionGraph. DIS triggers depend on the DIS service. Based on DIS events, DIS triggers can trigger function execution. To create DIS triggers, you need to enable the DIS service and configure Identity and Access Management (IAM) agencies for accessing the DIS service. |
||
The FGS.DmsEventMap element is used to create Distributed Message Service (DMS) trigger resources for FunctionGraph. DMS triggers depend on the DMS service. Based on DMS events, DMS triggers can trigger function execution. To create DMS triggers, you need to enable the DMS service first and configure the IAM agencies for accessing the DMS service. |
||
HuaweiCloud.FGS.Function is used to create function resources for FunctionGraph. |
||
The FGS.LtsEventMap element is used to create Log Tank Service (LTS) trigger resources for FunctionGraph. LTS triggers depend on the LTS service. To create LTS triggers, you need to enable the LTS service first. Based on LTS events, LTS triggers can trigger function execution. |
||
HuaweiCloud.FGS.ObsEventMap is used to create Object Storage Service (OBS) trigger resources for FunctionGraph. OBS triggers depend on the OBS service. Based on OBS trigger events, OBS triggers can trigger function execution. |
||
HuaweiCloud.FGS.TimerEventMap is used to create timer trigger resources for FunctionGraph. Timer triggers can periodically trigger function execution. |
||
The FGS.SmnEventMap element is used to create Simple Message Notification (SMN) trigger resources for FunctionGraph. SMN triggers depend on the SMN service. To create SMN triggers, you need to enable the SMN service first. Based on SMN events, SMN triggers can trigger function execution. |
||
Host Security Service (HSS) |
The HSS.Instance element is used to create HSS resources. |
|
Identity and Access Management (IAM) |
The IAM.Agency element is used to create agencies on IAM, specify entrusted accounts, and grant rights. After an administrator assigns agent operator permissions to an entrusted account user, the user can manage corresponding resources. |
|
The IAM.UserGroup element is used to create a user group. |
||
NAT Gateway |
The NAT.Instance element is used to create a NAT gateway instance. |
|
The NAT.SNatRule element is used to create a source NAT rule, which specifies the network segment for accessing the external network. |
||
Object Storage Service (OBS) |
The OBS.Bucket element is used to deploy bucket resources for HUAWEI CLOUD Object Storage Service (OBS). OBS provides a lot of secure, reliable, and low-cost data storage capabilities. Buckets are containers used to store objects. |
|
Relational Database Service (RDS) |
Relational Database Service (RDS) is a cloud-based web service that is reliable, scalable, easy to manage, and ready to use out-of-the-box. |
|
A database instance can contain multiple databases created by database users and can be accessed using the client tool and application program that are the same as those of an independent database instance. The RDS.MySQL.DataBase element can be used to create a database in a specified RDS instance. |
||
Database user accounts are used to connect to database instances and control the access to the database instances. For example, in a MySQL database, when a database instance is created, the root user account is created by default. |
||
RDS is a cloud-based web service that is reliable, scalable, easy to manage, and ready to use out-of-the-box. |
||
ServiceStage |
The ServiceStage.Agent element is compatible with original functions of ServiceStage. This element is about to be removed from AOS. You are advised to use CCE-related resources or the to-be-released AOS.Application element. |
|
The ServiceStage.AppGroup element is compatible with original functions of ServiceStage. This element is about to be removed from AOS. You are advised to use CCE-related resources or the to-be-released AOS.Application element. |
||
The ServiceStage.ContainerComponent element is compatible with the original functions of ServiceStage. This element is about to be removed from AOS. You are advised to use CCE-related resources or the to-be-released AOS.Application element. |
||
The ServiceStage.Job element is compatible with the original functions of ServiceStage. This element is about to be removed from AOS. You are advised to use CCE-related resources or the to-be-released AOS.Application element. |
||
The ServiceStage.StatefulApplication element is compatible with the original functions of ServiceStage. This element is about to be removed from AOS. You are advised to use CCE-related resources or the to-be-released AOS.Application element. |
||
The ServiceStage.StatelessApplication element is compatible with the original functions of ServiceStage. This element is about to be removed from AOS. You are advised to use CCE-related resources or the to-be-released AOS.Application element. |
||
Scalable File Service (SFS) |
SFS provides high-performance file storage which supports on-demand scaling. It can be shared by multiple ECSs. |
|
Simple Message Notification (SMN) |
The SMN.Subscription element is used to subscribe for SMN. |
|
The SMN.Topic element is used to create an SMN topic. |
||
Shared Load Balance |
The ULB.Healthmonitor element is a health check component of a shared load balancer. One pool corresponds to one HealthMonitor, and one HealthMonitor can manage multiple ECSs. You can add or delete the HealthMonitor as required. |
|
The ULB.Listener element indicates the listener under a shared load balancer. One shared load balancer corresponds to multiple listeners. You can add or delete listeners as required. |
||
The ULB.LoadBalancer element is used to deploy a shared load balancer at the PaaS layer. By creating such an object, you can provide a unified entry address for a group of containerized applications with the same functions, and distribute requests in load balancing mode to backend container applications. Shared load balancers are applicable to web services with high access traffic. They forward requests based on domain names or URLs, making request routing more flexible. Compared with classic load balancers, shared load balancers provide stronger HTTP and HTTPS forwarding capabilities, and better forwarding performance and stability. |
||
The ULB.Member element indicates an ECS under a shared load balancer. One pool corresponds to multiple ECSs. You can add or delete ECSs as required. |
||
The ULB.Pool element indicates an ECS group under a shared load balancer. One listener corresponds to multiple ECS groups. You can add or delete ECS groups as required. An ECS group consists of multiple ECSs. |
||
VPC Endpoint (VPCEP) |
The VPCEndpoint.Endpoint element is used to create a VPC endpoint. VPC endpoints are channels for connecting VPCs to VPC endpoint services. |
|
The VPCEndpoint.EndpointService element is used to create a VPC endpoint service. VPC endpoint services are cloud services or users' private services configured in VPCEP. |
||
Virtual Private Cloud (VPC) |
VPC.EIP is used to create a public elastic IP address. A public elastic IP address is a static IP address. You can bind or unbind an elastic IP address to an Elastic Cloud Server (ECS) in a subnet. An ECS in a Virtual Private Cloud (VPC) can access the Internet through a fixed public IP address. |
|
A firewall group (a logical group) is an access control policy system for one or more subnets. Based on the ingress and egress rules of associated subnets, firewalls determine whether data packets can be received by or sent into associated subnets. |
||
ACL policies in the outbound direction belong to ACL group members. One policy can contain multiple ACL rules. |
||
ACL policies in the inbound direction belong to ACL group members. One policy can contain multiple ACL rules. |
||
The VPC.FirewallRule element can be used to create ACL rules for subnet access control. |
||
A security group (a logical group) is a collection of access control policies for ECSs that have the same security protection requirements and are mutually trusted in a VPC. |
||
A security group rule is an access policy added for an ECS to implement access control. |
||
The VPC.Subnet element is used to create a subnet on a Huawei VPC. |
||
The VPC.VIP element is used to create a virtual IP address, that is, an IP address which has not been allocated to an ECS NIC. The ECS can be accessed through this virtual IP address. |
||
VPC.VPC is used to create a VPC network for Huawei public cloud products. |
||
Vulnerability Scan Service (VSS) |
VSS provides one-stop security detection services, including website vulnerability scanning, OS vulnerability scanning, asset compliance check, configuration baseline scanning, and weak password scanning, meeting standards compliance requirements. |
|
Web Application Firewall (WAF) |
WAF examines and protects website service traffic from multiple dimensions. Together with deep learning, WAF intelligently identifies malicious requests and prevents unknown threats. It also avoids common attacks such as SQL injection and cross-site scripting so that these attacks will not affect availability or security, or consume too much resources, reducing the risk of data tampering and theft. |
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.