Bills
You can view the resource usages and bills for different billing cycles under Dashboard in Billing Center.
Bill Generation
- After a package is paid, a bill will be generated in the billing system in real time for settlement. To view the remaining quota and usage details of a package, go to the Resource Packages page in Billing Center. For details, see Resource Packages.
- Pay-per-use resources are billed by the hour, day, or month, depending on the resource type. Pay-per-use CCE Autopilot clusters are settled by the hour.
You are not billed immediately after a record is generated. For example, if a pay-per-use CCE Autopilot cluster (billed hourly) is deleted at 08:30, you will still have expenditures for the 08:00 to 09:00 hour, but you will not be billed for the 08:00 to 09:00 hour until about 10:00. On the Expenditure Details page (go to Billing Center and choose Billing > Expenditure Details), Expenditure Time lists the usage duration of your pay-per-use resources.
Viewing Bills of a Specific Resource
- Log in to the CCE console and click the cluster name to access the cluster console.
- On the cluster overview page, copy the cluster ID.
Figure 1 Obtaining the cluster ID
- Go to Billing Center, choose Billing > Expenditure Details, select Resource ID as the filter, enter the resource ID copied in the previous step, and click the
icon to search for the bills of the resource.
Figure 2 Searching for a billIn this example, the bill details are displayed by usage and billing cycle. You can also select other statistical dimensions or periods.
Checking the Consistency of the Actual Usage and Billed Usage
Assume that you purchased a pay-per-use CCE Autopilot cluster in AP-Bangkok at 10:09:06 on April 08, 2024 and then deleted it at 12:09:06 on April 08, 2024. Table 1 describes the cluster details, including the cluster management, and vCPU and memory required by pods. (VPC endpoints are automatically created during cluster creation.)
For ease of description, assume that all the resources involved were created at the same time. There may be a time difference of several seconds. You can view the actual time on the console.
Unit prices in this example are used for reference only, and the calculated prices are only estimates. As unit prices change from time to time, the prices shown here will differ from actual prices. For details, see the data released on the Huawei Cloud official website.
You can view the transaction records of a CCE Autopilot cluster on the Bills > Expenditure Details page in Billing Center. The usage duration of a pay-per-use cluster is calculated by the second and billed on an hourly basis. You can check the actual usages in a billing cycle against the transaction record. For details, see Table 2, Table 3, and Table 4.
- Table 2 describes the cluster management expenditures. Three transaction records were generated.
- Table 3 describes the VPC endpoint expenditures. Two VPC endpoints (one for API Server and one for SWR) are required. Three transaction records were generated for each VPC endpoint. A total of six transaction records were generated.
- Table 4 describes the expenditures on the pods for running the add-ons. There were four pods. For each pod, one transaction record was generated for the vCPUs and one for the memory every hour. A total of 24 transaction records were generated.
Service Type |
CCE |
---|---|
Resource Type |
CCE Autopilot cluster |
Billing Mode |
Pay-per-use |
Expenditure Time |
From 10:09:06 on April 8, 2023 to 12:09:06 on April 8, 2023, three transaction records were generated in the following periods:
|
List Price |
List price = Unit price of the cluster management × Required duration In this example, the cluster was used for 3,054 seconds in the first billing cycle. If the unit price is $0.1 USD/hour, the list price is calculated as follows: 0.1 × (3,054/3,600) = $0.08483333 USD. Similarly, you can calculate the list price for the other periods. For details, see CCE Pricing Details. |
Discounted Amount |
Discounts offered for cloud services, for example, commercial discounts, partner authorized discounts, and promotional discounts. The discounted amount is based on the list price. |
Truncated Amount |
Huawei Cloud billing is calculated to the 8th decimal place. However, the amount due is truncated to the 2nd decimal place. The third and later decimal places are referred to as the truncated amounts. Take the first period as an example. The truncated amount is $0.00483333 USD. |
Amount Due |
Amount due = List price – Discount amount – Truncated amount Take the first period as an example. If the discount amount is 0, the amount due is $0.08 USD (0.08483333 – 0 – 0.00483333). |
Service Type |
VPC |
---|---|
Product |
VPC Endpoint |
Billing Mode |
Pay-per-use |
Expenditure Time |
From 10:09:06 on April 8, 2023 to 12:09:06 on April 8, 2023, six transaction records were generated for three periods. Two transaction records were generated in each period.
|
List Price |
List price = Unit price of VPC endpoint × Required duration In this example, two transaction records were generated in the first period, one for the VPC endpoint for API Server and the other for the VPC endpoint for SWR. Both VPC endpoints were used for 3,054 seconds, and the unit price is $0.014 USD/hour.
Similarly, you can calculate the list price for the other periods. For details, see VPC Endpoint Pricing. |
Discounted Amount |
Discounts offered for cloud services, for example, commercial discounts, partner authorized discounts, and promotional discounts. It is the discounted amount based on the list price. |
Truncated Amount |
Huawei Cloud billing is calculated to the 8th decimal place. However, the amount due is truncated to the 2nd decimal place. The third and later decimal places are referred to as the truncated amounts. The following uses the first period as an example:
|
Amount Due |
Amount due = List price – Discount amount – Truncated amount Take the first period as an example. Assume that the discounted amount is 0.
|
Service Type |
CCI |
---|---|
Product |
CCI - Autopilot Resources |
Billing Mode |
Pay-per-use |
Expenditure Time |
From 10:09:06 on April 8, 2023 to 12:09:06 on April 8, 2023, 24 transaction records were generated for three periods. Four transaction records were generated for vCPUs and four transaction records for memory in each period.
|
List Price |
vCPU list price = Unit price × Number of vCPUs × Required duration Memory list price = Unit price × Memory size × Required duration In this example, in the first period, the unit price of vCPUs is $0.043 USD/hour per vCPU, and the unit price of memory is $0.005 USD/hour per GiB. As the number of vCPUs and memory of the four pods are the same, their transaction records are the same.
Similarly, you can calculate the list price for the other periods. For details about the pricing of vCPUs and memory required by pods, see CCE Pricing Details. |
Discounted Amount |
Discounts offered for cloud services, for example, commercial discounts, partner authorized discounts, and promotional discounts. The discounted amount is based on the list price. |
Truncated Amount |
Huawei Cloud billing is calculated to the 8th decimal place. However, the amount due is truncated to the 2nd decimal place. The third and later decimal places are referred to as the truncated amounts. The following uses the first period as an example:
|
Amount Due |
Amount due = List price – Discount amount – Truncated amount Take the first period as an example. Assume that the discounted amount is 0.
|
You can view the detailed bills of a CCE Autopilot cluster on the Bills > Expenditure Details page in Billing Center. Bill details can be displayed in multiple dimensions. Generally, you can set the statistical dimension to usage and statistical period to billing cycle to collect statistics on the total expenditures in a month. You can check the expenditures in each bill against the actual expenditures. For details, see Table 5, Table 6, and Table 7.
- Table 5 describes the cluster management expenditures. There is only one bill.
- Table 6 describes the VPC endpoint expenditures. Two VPC endpoints (one for API Server and one for SWR) are required. One bill was generated for each VPC endpoint.
- Table 7 describes the expenditures on the pods for running the add-ons. There were four pods. For each pod, one bill was generated for the vCPUs and one for the memory. A total of eight bills were generated.
Service Type |
CCE |
---|---|
Resource Type |
CCE Autopilot cluster |
Billing Mode |
Pay-per-use |
Resource Name/ID |
Specific cluster name and ID. Example: ap-test, 4cdeb1cd-7071-4890-9ce4-e6c2299e960e |
Specifications |
Cluster management |
Usage Type |
Duration for pay-per-use billing |
Unit Price |
In pay-per-use billing, the unit price is only provided in simple pricing (resource usage × unit price). No unit price is provided in other pricing modes, for example, tiered pricing of EIP bandwidths. Simple pricing is used for pay-per-use clusters. For details, see CCE Pricing Details. |
Unit |
USD/hour |
Usage |
Depends on the unit of the unit price, which, for a CCE cluster, is USD/hour. Resource usage is billed by hour. In this example, the total usage duration is 2 hours. |
Usage Unit |
Hour |
List Price |
List price = Unit price of the cluster management × Required duration In this example, the cluster was used for 2 hours. If the unit price is $0.1 USD/hour, the list price is calculated as follows: 0.1 × 2 = $0.2 USD. |
Discounted Amount |
Discounts offered for cloud services, for example, commercial discounts, partner authorized discounts, and promotional discounts. The discounted amount is based on the list price. |
Amount Due |
Amount that should be paid for used cloud services after discounts are applied. |
Service Type |
VPC |
---|---|
Product |
VPC Endpoint |
Billing Mode |
Pay-per-use |
Resource Name/ID |
Name and ID of each VPC endpoint. Example: --, d4797c33-xxx-xxx-xxx-45963dbaf043 |
Specifications |
Basic edition |
Usage Type |
Duration for pay-per-use billing |
Unit Price |
In pay-per-use billing, the unit price is only provided in simple pricing (resource usage × unit price). No unit price is provided in other pricing modes, for example, tiered pricing of EIP bandwidths. Simple pricing is used for pay-per-use VPC endpoints. For details, see VPC Endpoint Pricing. |
Unit |
USD/hour |
Usage |
Depends on the unit of the unit price, which is USD/hour. Resource usage is billed by the hour. In this example, the total usage duration is 2 hours. |
Usage Unit |
Hour |
List Price |
List price = Unit price of VPC endpoint × Required duration In this example, the cluster was used for 2 hours and the unit price is $0.014 USD/hour. The list price in each bill is: 0.014 × 2 = $0.028 USD. |
Discounted Amount |
Discounts offered for cloud services, for example, commercial discounts, partner authorized discounts, and promotional discounts. The discounted amount is based on the list price. |
Amount Due |
Amount that should be paid for used cloud services after discounts are applied. |
Service Type |
CCI |
---|---|
Product |
CCI - Autopilot Resources |
Billing Mode |
Pay-per-use |
Resource Name/ID |
Pod name and CPU/memory ID. Example:
|
Specifications |
Autopilot general-computing CPU or Autopilot general-computing memory resources |
Usage Type |
Duration for pay-per-use billing |
Unit Price |
In pay-per-use billing, the unit price is only provided in simple pricing (resource usage × unit price). No unit price is provided in other pricing modes, for example, tiered pricing of EIP bandwidths. Simple pricing is used for pay-per-use vCPU and memory. For details about the pricing of vCPUs and memory required by pods, see CCE Pricing Details. |
Unit |
USD/s |
Usage |
Depends on the unit of the unit price, which is USD/s. Resource usage is billed by the second. In this example, the total usage duration is 7,200 seconds. |
Usage Unit |
Second |
List Price |
vCPU list price = CPU unit price × Required duration Memory list = Memory unit price × Required duration In this example, the usage duration is 7,200 seconds.
|
Discounted Amount |
Discounts offered for cloud services, for example, commercial discounts, partner authorized discounts, and promotional discounts. The discounted amount is based on the list price. |
Amount Due |
Amount that should be paid for used cloud services after discounts are applied. |
You can view the transaction records of a CCE Autopilot cluster on the Bills > Expenditure Details page in Billing Center. The usage duration of a pay-per-use cluster is calculated by the second and billed on an hourly basis. You can check the actual usages in a billing cycle against the transaction record. For details, see Table 2, Table 3, and Table 4.
- Table 2 describes the cluster management expenditures. Three transaction records were generated.
- Table 3 describes the VPC endpoint expenditures. Two VPC endpoints (one for API Server and one for SWR) are required. Three transaction records were generated for each VPC endpoint. A total of six transaction records were generated.
- Table 4 describes the expenditures on the pods for running the add-ons. There were four pods. For each pod, one transaction record was generated for the vCPUs and one for the memory every hour. A total of 24 transaction records were generated.
Service Type |
CCE |
---|---|
Resource Type |
CCE Autopilot cluster |
Billing Mode |
Pay-per-use |
Expenditure Time |
From 10:09:06 on April 8, 2023 to 12:09:06 on April 8, 2023, three transaction records were generated in the following periods:
|
List Price |
List price = Unit price of the cluster management × Required duration In this example, the cluster was used for 3,054 seconds in the first billing cycle. If the unit price is $0.1 USD/hour, the list price is calculated as follows: 0.1 × (3,054/3,600) = $0.08483333 USD. Similarly, you can calculate the list price for the other periods. For details, see CCE Pricing Details. |
Discounted Amount |
Discounts offered for cloud services, for example, commercial discounts, partner authorized discounts, and promotional discounts. The discounted amount is based on the list price. |
Truncated Amount |
Huawei Cloud billing is calculated to the 8th decimal place. However, the amount due is truncated to the 2nd decimal place. The third and later decimal places are referred to as the truncated amounts. Take the first period as an example. The truncated amount is $0.00483333 USD. |
Amount Due |
Amount due = List price – Discount amount – Truncated amount Take the first period as an example. If the discount amount is 0, the amount due is $0.08 USD (0.08483333 – 0 – 0.00483333). |
Service Type |
VPC |
---|---|
Product |
VPC Endpoint |
Billing Mode |
Pay-per-use |
Expenditure Time |
From 10:09:06 on April 8, 2023 to 12:09:06 on April 8, 2023, six transaction records were generated for three periods. Two transaction records were generated in each period.
|
List Price |
List price = Unit price of VPC endpoint × Required duration In this example, two transaction records were generated in the first period, one for the VPC endpoint for API Server and the other for the VPC endpoint for SWR. Both VPC endpoints were used for 3,054 seconds, and the unit price is $0.014 USD/hour.
Similarly, you can calculate the list price for the other periods. For details, see VPC Endpoint Pricing. |
Discounted Amount |
Discounts offered for cloud services, for example, commercial discounts, partner authorized discounts, and promotional discounts. It is the discounted amount based on the list price. |
Truncated Amount |
Huawei Cloud billing is calculated to the 8th decimal place. However, the amount due is truncated to the 2nd decimal place. The third and later decimal places are referred to as the truncated amounts. The following uses the first period as an example:
|
Amount Due |
Amount due = List price – Discount amount – Truncated amount Take the first period as an example. Assume that the discounted amount is 0.
|
Service Type |
CCI |
---|---|
Product |
CCI - Autopilot Resources |
Billing Mode |
Pay-per-use |
Expenditure Time |
From 10:09:06 on April 8, 2023 to 12:09:06 on April 8, 2023, 24 transaction records were generated for three periods. Four transaction records were generated for vCPUs and four transaction records for memory in each period.
|
List Price |
vCPU list price = Unit price × Number of vCPUs × Required duration Memory list price = Unit price × Memory size × Required duration In this example, in the first period, the unit price of vCPUs is $0.043 USD/hour per vCPU, and the unit price of memory is $0.005 USD/hour per GiB. As the number of vCPUs and memory of the four pods are the same, their transaction records are the same.
Similarly, you can calculate the list price for the other periods. For details about the pricing of vCPUs and memory required by pods, see CCE Pricing Details. |
Discounted Amount |
Discounts offered for cloud services, for example, commercial discounts, partner authorized discounts, and promotional discounts. The discounted amount is based on the list price. |
Truncated Amount |
Huawei Cloud billing is calculated to the 8th decimal place. However, the amount due is truncated to the 2nd decimal place. The third and later decimal places are referred to as the truncated amounts. The following uses the first period as an example:
|
Amount Due |
Amount due = List price – Discount amount – Truncated amount Take the first period as an example. Assume that the discounted amount is 0.
|
You can view the detailed bills of a CCE Autopilot cluster on the Bills > Expenditure Details page in Billing Center. Bill details can be displayed in multiple dimensions. Generally, you can set the statistical dimension to usage and statistical period to billing cycle to collect statistics on the total expenditures in a month. You can check the expenditures in each bill against the actual expenditures. For details, see Table 5, Table 6, and Table 7.
- Table 5 describes the cluster management expenditures. There is only one bill.
- Table 6 describes the VPC endpoint expenditures. Two VPC endpoints (one for API Server and one for SWR) are required. One bill was generated for each VPC endpoint.
- Table 7 describes the expenditures on the pods for running the add-ons. There were four pods. For each pod, one bill was generated for the vCPUs and one for the memory. A total of eight bills were generated.
Service Type |
CCE |
---|---|
Resource Type |
CCE Autopilot cluster |
Billing Mode |
Pay-per-use |
Resource Name/ID |
Specific cluster name and ID. Example: ap-test, 4cdeb1cd-7071-4890-9ce4-e6c2299e960e |
Specifications |
Cluster management |
Usage Type |
Duration for pay-per-use billing |
Unit Price |
In pay-per-use billing, the unit price is only provided in simple pricing (resource usage × unit price). No unit price is provided in other pricing modes, for example, tiered pricing of EIP bandwidths. Simple pricing is used for pay-per-use clusters. For details, see CCE Pricing Details. |
Unit |
USD/hour |
Usage |
Depends on the unit of the unit price, which, for a CCE cluster, is USD/hour. Resource usage is billed by hour. In this example, the total usage duration is 2 hours. |
Usage Unit |
Hour |
List Price |
List price = Unit price of the cluster management × Required duration In this example, the cluster was used for 2 hours. If the unit price is $0.1 USD/hour, the list price is calculated as follows: 0.1 × 2 = $0.2 USD. |
Discounted Amount |
Discounts offered for cloud services, for example, commercial discounts, partner authorized discounts, and promotional discounts. The discounted amount is based on the list price. |
Amount Due |
Amount that should be paid for used cloud services after discounts are applied. |
Service Type |
VPC |
---|---|
Product |
VPC Endpoint |
Billing Mode |
Pay-per-use |
Resource Name/ID |
Name and ID of each VPC endpoint. Example: --, d4797c33-xxx-xxx-xxx-45963dbaf043 |
Specifications |
Basic edition |
Usage Type |
Duration for pay-per-use billing |
Unit Price |
In pay-per-use billing, the unit price is only provided in simple pricing (resource usage × unit price). No unit price is provided in other pricing modes, for example, tiered pricing of EIP bandwidths. Simple pricing is used for pay-per-use VPC endpoints. For details, see VPC Endpoint Pricing. |
Unit |
USD/hour |
Usage |
Depends on the unit of the unit price, which is USD/hour. Resource usage is billed by the hour. In this example, the total usage duration is 2 hours. |
Usage Unit |
Hour |
List Price |
List price = Unit price of VPC endpoint × Required duration In this example, the cluster was used for 2 hours and the unit price is $0.014 USD/hour. The list price in each bill is: 0.014 × 2 = $0.028 USD. |
Discounted Amount |
Discounts offered for cloud services, for example, commercial discounts, partner authorized discounts, and promotional discounts. The discounted amount is based on the list price. |
Amount Due |
Amount that should be paid for used cloud services after discounts are applied. |
Service Type |
CCI |
---|---|
Product |
CCI - Autopilot Resources |
Billing Mode |
Pay-per-use |
Resource Name/ID |
Pod name and CPU/memory ID. Example:
|
Specifications |
Autopilot general-computing CPU or Autopilot general-computing memory resources |
Usage Type |
Duration for pay-per-use billing |
Unit Price |
In pay-per-use billing, the unit price is only provided in simple pricing (resource usage × unit price). No unit price is provided in other pricing modes, for example, tiered pricing of EIP bandwidths. Simple pricing is used for pay-per-use vCPU and memory. For details about the pricing of vCPUs and memory required by pods, see CCE Pricing Details. |
Unit |
USD/s |
Usage |
Depends on the unit of the unit price, which is USD/s. Resource usage is billed by the second. In this example, the total usage duration is 7,200 seconds. |
Usage Unit |
Second |
List Price |
vCPU list price = CPU unit price × Required duration Memory list = Memory unit price × Required duration In this example, the usage duration is 7,200 seconds.
|
Discounted Amount |
Discounts offered for cloud services, for example, commercial discounts, partner authorized discounts, and promotional discounts. The discounted amount is based on the list price. |
Amount Due |
Amount that should be paid for used cloud services after discounts are applied. |
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot