Billed Items

When using the CCE service, you will be billed for clusters and other cloud service resources.

Billed Items for CCE Standard and Turbo Clusters

Figure 1 Billed CCE items

The billed items marked with asterisks (*) are mandatory.

**Table 1** Billing composition
Billed Item	Description	Billing Mode	Formula
*Cluster	Cluster management. The price varies depending on the region where each cluster is located, the number of master nodes (HA or not), and the maximum number of worker nodes. You do not need to pay for the management of a hibernated cluster, but the cloud service resources used in the cluster, such as EVS disks, EIPs, and bandwidths will be charged in their own billing modes.	Yearly/Monthly or pay-per-use	Unit price of the cluster flavor x Required duration For details, see CCE Pricing Details.
Other cloud service resources	Cloud service resources that are used in a cluster and created either manually or automatically, such as ECSs, EVS disks, OBS storage, EIPs, and load balancers. Although cloud service resources can be created on the CCE console, their billed items and bills are independent of those of CCE clusters. For details, see Table 2.	Respective billing modes	None

The following table lists the cloud service resources that may be used in a CCE standard or Turbo cluster. These resources are billed separately.

**Table 2** Billed items of other cloud service resources
Billed Item	Description	Billing Mode	Formula
ECS	ECS flavor: When purchasing a node, ensure that the number of vCPUs is greater than or equal to 2 and the memory is greater than or equal to 4 GiB. Billed by ECS flavor, including vCPUs and memory. Computing and storage capabilities vary by the number of vCPUs and memory size. Most nodes are no longer billed after they are stopped. An ECS with a local disk attached (such as a disk-intensive or ultra-high I/O ECS) will continue to be billed after the ECS is stopped. For details, see Billing.	Yearly/Monthly or pay-per-use	Unit price of the ECS flavor x Required duration For details, see ECS Pricing Details.
	EVS disks (including system disks and data disks): When purchasing a node, you must purchase system disks and data disks. System disk: The default capacity is 50 GiB. You can adjust the capacity as required. Data disk: The default capacity is 100 GiB. You can adjust the capacity (no less than 20 GiB). You can also add more data disks as needed. Billed by EVS disk type and capacity. Regardless of whether you use the disk after purchasing it, you will be charged right away. For details, see Billing.	Yearly/Monthly or pay-per-use	Unit price of an EVS disk x EVS disk capacity x Required duration For details, see EVS Pricing Details.
	(Optional) EIP: To access the Internet from a node, you need to purchase an EIP. Billed by the EIP and bandwidth or traffic. EIP for a yearly/monthly node: billed by bandwidth EIP for a pay-per-use node: billed by bandwidth or traffic. You are charged for the EIP no matter if it is not bound to any instance. When you purchase a node on the CCE console, a pay-per-use EIP cannot be added to a shared bandwidth. Go to the EIP console to add it to a shared bandwidth. For details, see Billing Composition.	Yearly/Monthly or pay-per-use	Tiered pricing based on fixed bandwidth. 0 Mbit/s to 5 Mbit/s (included): Bandwidth x Price per Mbit/s of bandwidth less than 5 Mbit/s Greater than 5 Mbit/s: 5 x Price per Mbit/s of bandwidth less than 5 Mbit/s + (Bandwidth – 5) x Price per Mbit/s of bandwidth more than 5 Mbit/s By traffic: EIP traffic x Unit price For details, see EIP Pricing Details.
ELB	Used by the Services and Ingresses created in a cluster. A load balancer automatically created on the CCE console is billed on the pay-per-use basis only. Billed by: Shared load balancer: load balancer, and EIP (billed by bandwidth or traffic) Dedicated load balancer: the number of AZs, load balancer, and EIP (billed by bandwidth or traffic) For details, see Billing.	Yearly/Monthly or pay-per-use	Shared load balancer: Unit price x Required duration + EIP Dedicated load balancer: Number of AZs x Unit price x Required duration + EIP For details, see ELB Pricing Details.
NAT Gateway	NAT gateways cannot be automatically created on the CCE console. Buy them on the NAT Gateway console. Billed by instance. For details, see Billing.	Yearly/Monthly or pay-per-use	Unit price x Required duration For details, see NAT Gateway Pricing Details.
EVS	Mounted to the workloads in a cluster. An EVS disk automatically created on the CCE console is billed on the pay-per-use basis only. Billed by EVS disk type and capacity. Regardless of whether you use the disk after purchasing it, you will be charged right away. For details, see Billing.	Yearly/Monthly or pay-per-use	Unit price x Purchase duration For details, see EVS Pricing Details.
OBS	Mounted to the workloads in a cluster. A parallel file system is recommended. OBS storage automatically created on the CCE console is billed on the pay-per-use basis only. Billed by storage space, requests, traffic (free for intranet traffic), and data retrievals (only for Archive storage). For details, see Billing.	Yearly/Monthly (resource packages) and pay-per-use	Storage unit price x Storage space x Required duration + Traffic request unit price x Number of requests + Unit price of outbound Internet traffic (by time) x Outbound Internet traffic volume+ Data retrieval unit price (by retrieval speed) x Data retrieved For details, see OBS Pricing Details.
Scalable File Service (SFS)	Mounted to the workloads in a cluster. An SFS system automatically created on the CCE console is billed on the pay-per-use basis only. Billed by storage space. For details, see Billing.	Yearly/Monthly or pay-per-use	Storage unit price x Storage space x Required duration For details, see SFS Pricing Details.
SFS Turbo	Mounted to the workloads in a cluster. SFS Turbo systems cannot be automatically created on the CCE console. Manually create them on the SFS Turbo console. Billed by storage space and bandwidth (only for HPC-cached SFS Turbo systems). For details, see Billing.	Yearly/Monthly or pay-per-use	Storage unit price x Storage space x Required duration + Bandwidth (only for HPC-cached SFS Turbo systems) x Required duration For details, see SFS Pricing Details.