Billing Items

When using CCE Autopilot, you will be billed for cluster management, pods, VPC endpoints, and other cloud service resources.

CCE Autopilot Billing Items

Figure 1 Billing items
Click to enlarge

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

**Table 1** Price of a CCE Autopilot cluster
Billing Item	Description	Billing Mode	Formula
*Cluster management	The expenditures for managing the cluster NOTE: If a cluster is frozen, workloads in the cluster will be in the pending state and will not be rescheduled until the cluster is unfrozen.	Pay-per-use	Unit price of cluster management × Required duration For details about the unit prices of cluster management, see Unit Prices in Pay-per-Use Billing.
*Pods	Billed based on the vCPU, memory, and temporary storage specifications. NOTICE: If a specification is not supported, it will be automatically upgraded to a higher one. For example, if all containers in a pod require 2 vCPUs and 3 GiB of memory, the specification is automatically upgraded to 2 vCPUs and 4 GiB of memory. Specification Description lists the specifications supported by CCE Autopilot. By default, 30-GiB free ephemeral storage is allocated to each pod (with an IOPS upper limit of 2,500 and a burst limit of 16,000). Any storage space that exceeds 30 GiB will be billed separately.	Pay-per-use and packages (CPU and/or memory)	Unit price of the pod specification × Required duration For details about the unit prices of pod specifications, see Unit Prices in Pay-per-Use Billing.
*VPC endpoints	CCE Autopilot clusters connect to other cloud services such as SWR through VPC endpoints, which are billed separately based on the number of VPC endpoints you are using.	Pay-per-use	Unit price of the VPC endpoint × Required duration For details about the unit prices of VPC endpoint specifications, see VPC Endpoint Price Calculator. NOTE: If a VPC endpoint connects to a VPC endpoint service other than DNS or OBS, you will be billed for how long you use this VPC endpoint. If a VPC endpoint connects to DNS or OBS, you will not be billed for this VPC endpoint. See the pricing on the VPC Endpoint console.
Other cloud resources	Resources of cloud services used by a cluster such as ELB are billed based on their pricing rules, no matter whether these resources are automatically created or manually added during cluster creation and use. Although cloud resources can be created on the CCE console, their billing items and bills are independent of those of CCE clusters.	Respective billing modes	For details, see Price Calculator.

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

**Table 2** Billing items of other cloud service resources
Billing Item	Description	Billing Mode	Formula
ELB	Used when a Service or ingress is created in a cluster. A load balancer is automatically created and billed on a pay-per-use basis. Billing factor: 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	Dedicated load balancer: Number of AZs × Unit price × Required duration + EIP price For details, see ELB Pricing Details.
NAT Gateway	Used when SNAT is configured for the cluster. A NAT gateway is automatically created and billed on a pay-per-use basis. Billing factor: NAT gateway specifications For details, see Billing.	Yearly/Monthly or pay-per-use	Unit price × Required duration For details, see NAT Gateway Pricing Details.
EVS	Used for persistent storage for the workloads in the cluster. An EVS disk is automatically and billed on a pay-per-use basis. Billing factors: EVS disk type and disk space Regardless of whether you use the disk after purchasing it, you will be billed right away. For details, see Billing.	Yearly/Monthly or pay-per-use	Unit price × Purchase duration For details, see EVS Pricing Details.
OBS	Used for persistent storage for the workloads in the cluster. A parallel file system is recommended. An OBS bucket or parallel file system is automatically created and billed on a pay-per-use basis. Billing factors: 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 × Storage space × Required duration + Traffic request unit price × Number of requests + Unit price of outbound Internet traffic (by time period) × Outbound Internet traffic volume + Data retrieval unit price (by retrieval speed) × Data size retrieved For details, see OBS Pricing Details.
SFS	Used for persistent storage for the workloads in the cluster. A file system is automatically created and billed on a pay-per-use basis. Billing factor: storage space For details, see Billing.	Yearly/Monthly or pay-per-use	Storage unit price × Storage space × Required duration For details, see SFS Pricing Details.
SFS Turbo	Used for persistent storage for the workloads in the cluster. SFS Turbo file systems cannot be automatically created. You need to manually create them on the SFS Turbo console. Billing factors: storage space and bandwidth (only for HPC-cached SFS Turbo file systems) For details, see Billing.	Yearly/Monthly or pay-per-use	Storage unit price × Storage space × Required duration + Bandwidth (only for HPC-cached SFS Turbo file systems) × Required duration For details, see SFS Turbo Pricing Details.