Compute
Elastic Cloud Server
Huawei Cloud Flexus
Bare Metal Server
Auto Scaling
Image Management Service
Dedicated Host
FunctionGraph
Cloud Phone Host
Huawei Cloud EulerOS
Networking
Virtual Private Cloud
Elastic IP
Elastic Load Balance
NAT Gateway
Direct Connect
Virtual Private Network
VPC Endpoint
Cloud Connect
Enterprise Router
Enterprise Switch
Global Accelerator
Management & Governance
Cloud Eye
Identity and Access Management
Cloud Trace Service
Resource Formation Service
Tag Management Service
Log Tank Service
Config
OneAccess
Resource Access Manager
Simple Message Notification
Application Performance Management
Application Operations Management
Organizations
Optimization Advisor
IAM Identity Center
Cloud Operations Center
Resource Governance Center
Migration
Server Migration Service
Object Storage Migration Service
Cloud Data Migration
Migration Center
Cloud Ecosystem
KooGallery
Partner Center
User Support
My Account
Billing Center
Cost Center
Resource Center
Enterprise Management
Service Tickets
HUAWEI CLOUD (International) FAQs
ICP Filing
Support Plans
My Credentials
Customer Operation Capabilities
Partner Support Plans
Professional Services
Analytics
MapReduce Service
Data Lake Insight
CloudTable Service
Cloud Search Service
Data Lake Visualization
Data Ingestion Service
GaussDB(DWS)
DataArts Studio
Data Lake Factory
DataArts Lake Formation
IoT
IoT Device Access
Others
Product Pricing Details
System Permissions
Console Quick Start
Common FAQs
Instructions for Associating with a HUAWEI CLOUD Partner
Message Center
Security & Compliance
Security Technologies and Applications
Web Application Firewall
Host Security Service
Cloud Firewall
SecMaster
Anti-DDoS Service
Data Encryption Workshop
Database Security Service
Cloud Bastion Host
Data Security Center
Cloud Certificate Manager
Edge Security
Situation Awareness
Managed Threat Detection
Blockchain
Blockchain Service
Web3 Node Engine Service
Media Services
Media Processing Center
Video On Demand
Live
SparkRTC
MetaStudio
Storage
Object Storage Service
Elastic Volume Service
Cloud Backup and Recovery
Storage Disaster Recovery Service
Scalable File Service Turbo
Scalable File Service
Volume Backup Service
Cloud Server Backup Service
Data Express Service
Dedicated Distributed Storage Service
Containers
Cloud Container Engine
SoftWare Repository for Container
Application Service Mesh
Ubiquitous Cloud Native Service
Cloud Container Instance
Databases
Relational Database Service
Document Database Service
Data Admin Service
Data Replication Service
GeminiDB
GaussDB
Distributed Database Middleware
Database and Application Migration UGO
TaurusDB
Middleware
Distributed Cache Service
API Gateway
Distributed Message Service for Kafka
Distributed Message Service for RabbitMQ
Distributed Message Service for RocketMQ
Cloud Service Engine
Multi-Site High Availability Service
EventGrid
Dedicated Cloud
Dedicated Computing Cluster
Business Applications
Workspace
ROMA Connect
Message & SMS
Domain Name Service
Edge Data Center Management
Meeting
AI
Face Recognition Service
Graph Engine Service
Content Moderation
Image Recognition
Optical Character Recognition
ModelArts
ImageSearch
Conversational Bot Service
Speech Interaction Service
Huawei HiLens
Video Intelligent Analysis Service
Developer Tools
SDK Developer Guide
API Request Signing Guide
Terraform
Koo Command Line Interface
Content Delivery & Edge Computing
Content Delivery Network
Intelligent EdgeFabric
CloudPond
Intelligent EdgeCloud
Solutions
SAP Cloud
High Performance Computing
Developer Services
ServiceStage
CodeArts
CodeArts PerfTest
CodeArts Req
CodeArts Pipeline
CodeArts Build
CodeArts Deploy
CodeArts Artifact
CodeArts TestPlan
CodeArts Check
CodeArts Repo
Cloud Application Engine
MacroVerse aPaaS
KooMessage
KooPhone
KooDrive

Pay-per-Use Billing

Updated on 2024-11-04 GMT+08:00

Pay-per-use is a postpaid billing mode. If you expect to use resources flexibly, this billing mode is suitable for you. This section describes the billing rules for pay-per-use CCE resources.

Application Scenarios

Pay-per-use billing is good for short-term, bursty, or unpredictable workloads, such as applications for e-commerce flash sales, temporary testing, and scientific computing.

Billed Items

When using the CCE service, you can select a billing mode for items listed in Table 1 on the CCE console. The related cloud service resources automatically created on the CCE console are billed on a pay-per-use basis by default. For details, see their respective billing descriptions.

Table 1 Items billed on a pay-per-use basis

Billed Item

Resource Type

Description

Cluster

N/A

A cluster is billed on a pay-per-use basis based on the cluster scale and HA mode.

ECS

ECS flavor

vCPUs and memory are billed on a pay-per-use basis.

EVS disk

If an EVS disk (a system disk or a data disk) is created along with a pay-per-use ECS, the EVS disk is also billed on a pay-per-use basis.

EIP

An EIP billed by bandwidth or traffic can be bound to a pay-per-use ECS created on the CCE console, but cannot be added to a shared bandwidth on the CCE console. If you want to add an EIP to a shared bandwidth, purchase one on the EIP console and then bind it to the ECS.

If an EIP billed by bandwidth is purchased along with a pay-per-use ECS, the bandwidth is also billed on a pay-per-use basis.

Billed Usage Period

A pay-per-use CCE resource is calculated by the second and billed every hour (GMT+08:00). Once settlement is complete, it enters a new billed usage period. The billing starts when a cluster or node is launched and ends when the cluster or node is deleted.

NOTE:

It takes a certain time to launch a CCE cluster or node. The billing starts from the time when the cluster or node is successfully created. You can view the time in Operation Records on the CCE console.

For example, if you purchased a pay-per-use CCE cluster at 08:45:30 and deleted it at 08:55:30, you are billed for the 600 seconds from 08:45:30 to 08:55:30.

Impact of Arrears

Figure 1 shows the statuses a pay-per-use resource can have throughout its lifecycle. After a resource is purchased, it enters the valid period and runs normally during this period. If your account goes into arrears, the resource enters a grace period and then a retention period.

Figure 1 Lifecycle of a pay-per-use CCE resource

Arrears Reminder

You will be billed for pay-per-use resource after each billed usage period ends. If your account goes into arrears, we will notify you by email, SMS, or in-app message.

Impacts of Arrears

If there is no top-up account with sufficient balance and no other payment method configured to pay for the resource used, your account goes into arrears, and the resource enters the grace period. 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 balance as needed.

If you do not bring your account balance current before the grace period expires, the resource turns to Frozen and enters a retention period. You cannot perform any operations on a pay-per-use resource in the Frozen status.

After the retention period ends, CCE clusters and resources like nodes, EVS disks, and EIPs will be released and cannot be restored.

NOTE:

Billing for a Hibernated Cluster

Generally, after a pay-per-use CCE cluster is hibernated:

  • You will not be billed for the management of the cluster, but other cloud service resources like EVS disks and bandwidth in the cluster will still be billed in their own billing modes.
  • ECSs in the cluster will not stop automatically. To stop all the nodes, select Shut down all nodes in the cluster. You can also stop a node on the ECS console. For details, see Stopping a Node. For details about the billing policies after the nodes are stopped, see Billing Policies for a Stopped Node.
  • Resources on the master nodes will be released. If computing resources are insufficient, the subsequent cluster wakeup may fail.

For example, if you purchased a pay-per-use cluster with 50 worker nodes at 09:00:00 and hibernated it at 09:30:00, you are billed for the 30 minutes from 09:00:00 to 09:30:00 within the billed usage period from 09:00:00 to 10:00:00.

Billing Policies for a Stopped Node

Generally, after a pay-per-use node is stopped:

  • Basic resources (vCPUs and memory) will not be billed.
  • Other resources (EVS disks and bandwidth) used by the node are still charged.
  • Basic resources (vCPUs and memory) will be released, so ECS startup may fail. Wait a moment and try again.
  • Basic resources (vCPUs and memory) of ECSs created on a DeH or in an edge AZ will be retained.

If a local disk is attached to an ECS (such as a disk-intensive ECS or an ultra-high I/O ECS), basic resources (vCPUs, memory, and images) and other resources (EVS disks and bandwidth) are still billed after the ECS is stopped. To avoid any additional expenditures, delete the ECS and all its resources.

We use cookies to improve our site and your experience. By continuing to browse our site you accept our cookie policy. Find out more

Feedback

Feedback

Feedback

0/500

Selected Content

Submit selected content with the feedback