このページは、お客様の言語ではご利用いただけません。Huawei Cloudは、より多くの言語バージョンを追加するために懸命に取り組んでいます。ご協力ありがとうございました。
- Service Overview
- Billing
- Getting Started
-
User Guide
- Overview
- Permissions Management
- Environment Management
- Application Management
- Component Management
- Instance Management
- Component Configurations
- Component O&M
- System Settings
- Key Operations Recorded by CTS
-
Best Practices
- CAE Best Practices
- Using CAE to Host Nginx Static File Servers
- Interconnecting GitLab with Jenkins for Automatic Build and Deployment on CAE
- Deploying Components Based on the Dependency Sequence Using the Jenkins Pipeline
- Deploying Spring Cloud Applications to CAE to Automatically Connect to the Nacos Engine
- Graceful Startup of a Spring Cloud Application
- Health Check
- Lifecycle Management
- Sending Event Alarms to WeCom
-
Connecting to the CodeArts Pipeline to Automatically Upgrade CAE Components
- Overview
- Upgrading a CAE Component After Uploading a Software Package Built Using the Pipeline to a CodeArts Release Repo
- Upgrading a CAE Component After Uploading a Software Package Built Using the Pipeline to the OBS Bucket
- Upgrading a CAE Component After Uploading an Image Built Using the Pipeline to the SWR Image Repository
- Configuring PromQL to Implement Custom Auto Scaling
- Configuring the Interconnection Between CAE and DEW to Help Applications Obtain Encrypted Secrets from DEW
- Deploying ASP.NET Core Applications to CAE
- Connecting the Network Through Enterprise Routes
- API Reference
-
FAQs
- Component Management FAQs
- Environment Management
-
Component Configuration FAQs
- Is Manual Scaling Still Effective When a Scaling Policy Is Configured?
- Can Components Be Scaled Without a Scaling Policy?
- Why Is My Instance Abnormal After Cloud Storage Is Configured?
- What Do I Do If a Component Becomes Not Ready?
- How Does CAE Support Dark Launch?
- How Do I Provide Prometheus Metrics for a Java Application?
- System Configuration FAQs
- Service Resources FAQs
- General Reference
Copied.
Pay-per-Use
Application Scenario
Pay-per-use is a postpaid mode and is useful when application instances do not need to run 24/7, or only for a short period of time.
Billing Items
You are billed for the following items on a pay-per-use basis.
Billing Item |
Description |
---|---|
Compute resources |
vCPUs and memory are billed on your usage duration. Fees are calculated in minutes and billed by the hour. |
Traffic |
Billed on the amount of public network traffic you use, in GB. |
The price includes:
- vCPU: calculated by your vCPU configuration.
- Memory: calculated by your memory configuration.
- Traffic: calculated by your traffic volume.
Pricing Details
Billing Item |
Billing Cycle |
Unit |
Price (USD) |
||||
---|---|---|---|---|---|---|---|
AP-Singapore |
ME-Riyadh |
TR-Istanbul |
AF-Johannesburg |
LA-Mexico City2 |
|||
vCPU |
Hour |
core-minute |
0.0013483 |
0.0014158 |
0.0012 |
0.0014697 |
0.0018607 |
Memory |
Hour |
GiB-minute |
0.0001475 |
0.0001549 |
0.0001313 |
0.0001608 |
0.0002036 |
Traffic |
Hour |
GB |
0.114 |
0.117 |
0.0855 |
0.18 |
0.081 |
Billing Cycle
In pay-per-use mode, fees are calculated in minutes and billed by the hour (GMT+08:00:00). Once settlement is complete, a new billing cycle starts. Billing starts when a CAE instance is created and ends when it is deleted.
For example, if you deployed an application at 08:45:30 to provide services using compute resources (vCPUs and memory) and traffic, and then deleted it at 08:55:00, the billing cycle was from 08:00:00 to 09:00:00 with fees generated from 08:45:30 to 08:55:00. You were billed for 10 minutes.
Billing Example
You created an application and configured a 2 vCPU | 4 GiB component at 09:59:30 on Apr 18, 2023, and then deleted the application at 10:45:46 on Apr 18, 2023, using 0.8 GB of traffic data during application running. You were billed for:
- Usage of 1 minute from 09:59:30 to 10:00:00
- Usage of 46 minutes from 10:00:00 to 10:45:46
You were billed for each usage duration. CAE resources are billed individually as described in Table 3. You can choose to display either per-minute or per-hour prices in the pricing details.
Item |
Billing Formula |
---|---|
vCPU |
Instance specification unit price x Instance specifications x Usage duration |
Memory |
Instance specification unit price x Instance specifications x Usage duration |
Traffic |
Actual traffic usage |
Figure 1 shows how the total price is calculated.
The prices in the figure are for reference only. The actual calculation is subject to the prices in CAE Pricing Details.
Price Change After Specification Change
If you change the specifications of a pay-per-use CAE instance, the original order will become invalid and a new order will be placed. You will be billed based on the new specifications.
If you change instance specifications within a given hour, multiple billing records will be generated. The start time and end time of each record correspond to when different specifications took effect within the hour.
For example, if you created an application and configured a 1 vCPU | 2 GiB component at 09:00:00 and upgraded to 2 vCPU | 4 GiB at 09:30:00, two billing records were generated from 09:00:00 and 10:00:00.
- 1 vCPU | 2 GiB instance usage from 09:00:00 to 09:29:59
- 2 vCPU | 4 GiB instance usage from 09:30:00 to 10:00:00
Impact of Arrears
Figure 2 shows the statuses a pay-per-use CAE resource can go through throughout its lifecycle. After an instance is created, it enters a valid period and runs normally during this period. If your account falls into arrears, the resource enters a grace period and then a retention period.
Arrears Alert
The system will deduct fees for pay-per-use resources at the end of each billing cycle. When your account is in arrears, we will notify the Huawei Cloud account creator by email, SMS, and internal message.
Impact of Arrears
If your account balance is insufficient, your account falls into arrears. However, your pay-per-use resources will not be stopped immediately. There will be a grace period before they are stopped. You are still responsible for expenditures generated during the grace period. You can view the charges on the Billing Center > Overview page and pay any past due balances as needed.
If you do not settle your account balance before the grace period ends, the resource enters a retention period and its status becomes Frozen. You cannot perform any operations while it is in the retention period.
If you do not settle your account balance before the retention period ends, the resource will be released and data cannot be restored.
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