Bu sayfa henüz yerel dilinizde mevcut değildir. Daha fazla dil seçeneği eklemek için yoğun bir şekilde çalışıyoruz. Desteğiniz için teşekkür ederiz.

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
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

Billing

Updated on 2025-03-04 GMT+08:00

Billing Items

ECSs are billed based on ECS specifications and the service duration.

Table 1 ECS billing

Billing Item

Description

ECS

Pricing is based on the ECS type, flavor (including vCPUs and memory), service duration, and the number of purchased ECSs.

For pricing details, see Elastic Cloud Server Pricing Details.

Image

Public images for open-source OSs like Linux are free, while those for commercial OSs, such as Windows, are billed.

NOTE:

If a private image is created using an ECS created from a KooGallery image, you will be billed for the private image based on the pricing details in KooGallery.

EVS disk

EVS disks are mandatory. A system disk is 40 GB by default. EVS disks can be billed on a pay-per-use or yearly/monthly basis. For pricing details, see Elastic Volume Service Pricing Details. The usage duration of EVS disks should be the same as the associated ECS.

EIP

A public IP address is required for public accessibility. For pricing details, see Elastic IP Pricing Details.

Bandwidth

An EIP can be billed by bandwidth or traffic. For pricing details, see Billed by Bandwidth.

Billing Modes

An ECS can be billed on a pay-per-use, spot pricing, or yearly/monthly basis.

  • Yearly/Monthly: An ECS can be billed on a monthly or yearly basis.
  • Pay-per-use: An ECS can be billed by second. You can start or stop an ECS on demand at any time.
  • Spot pricing: An ECS will be billed based on the market price, which is gradually adjusted based on the supply-and-demand changes.

Table 2 lists the differences between the billing modes.

Table 2 Billing modes

Billing Mode

Yearly/Monthly

Pay-per-Use

Spot Pricing

Payment Method

Prepaid

Billed by the purchased duration specified in the order.

Postpaid

Billed by usage duration.

Postpaid

Billed at the market price, which varies according to the changes in supply and demand. The start price of the bill is the market price when the ECS was purchased, and then the ECS is billed at the market price on the hour.

Learn more about spot pricing

Billing Cycle

Billed by the purchased duration specified in the order.

Billed by the second and settled by the hour.

Billed by the second and settled by the hour.

Billing for Stopped ECS

Billed by the purchased duration specified in the order, regardless of whether the ECS is stopped or not.

  • After a common ECS (without local disks or FPGAs attached) is stopped, basic resources (vCPUs, memory, image, and GPUs) are not billed. Other resources (EVS disks, EIPs, and bandwidth) associated with the ECS will continue to be billed.
  • An ECS with local disks attached, an FPGA-based ECS, or a bare metal ECS will continue to generate expenditures even after being stopped. Its vCPUs and memory are retained. To avoid being billed for such an ECS, delete it and its associated resources.
  • After a common ECS (without local disks or FPGAs attached) is stopped, basic resources (vCPUs, memory, image, and GPUs) are not billed. Other resources (EVS disks, EIPs, and bandwidth) associated with the ECS will continue to be billed.
  • An ECS with local disks attached, an FPGA-based ECS, or a bare metal ECS will continue to generate expenditures even after being stopped. Its vCPUs and memory are retained. To avoid being billed for such an ECS, delete it and its associated resources.

Billing Mode Change

Can be changed to pay-per-use.

Changing Yearly/Monthly to Pay-per-Use

Can be changed to yearly/monthly.

Changing Pay-per-Use to Yearly/Monthly

Cannot be changed to pay-per-use or yearly/monthly.

Specification Modification

Supported

Supported

Not supported

Application Scenarios

This cost-effective mode is ideal when the duration of ECS usage is predictable. The yearly/monthly mode is recommended for long-term users.

This billing mode is ideal for scenarios where resource demands fluctuate and you want more flexibility on resource usage.

Spot ECSs can be reclaimed at any time and are suitable for stateless, fault-tolerant instances that are not sensitive to interruptions.

  • Yearly/Monthly: This billing mode provides a larger discount than pay-per-use and is recommended for long-term users. A yearly/monthly ECS is billed based on the purchased duration specified in the order.
  • Pay-per-use: This billing mode is flexible with the billing accurately down to the second.

    An ECS is billed from the time when it is provisioned to the time when it is deleted.

    Common ECSs refer to ECSs without local disks or FPGAs attached. After a common ECS is stopped, it is billed as follows:
    • ECS basic resources (vCPUs, memory, image, and GPUs) no longer generate expenditures. Its associated resources such as its EVS disks, EIPs, and bandwidth will continue to be billed.
    • When you try to start the ECS the next time, the system will allocate vCPUs and memory again, but if resources are insufficient, the startup may fail. In this case, you can try again later or resize the ECS specifications first before trying to start it.
    Special pay-per-use ECSs will continue to be billed after being stopped and its resources such as vCPUs and memory are still retained.
    NOTE:

    Special ECSs include:

    • Bare metal ECSs
    • ECSs attached with local disks, such as disk-intensive ECSs and ultra-high I/O ECSs
    • FPGA-based ECSs

    To stop billing for special ECSs, delete them and their associated resources.

  • Spot pricing

    Price: Spot ECSs are billed based on the market price, which varies according to the changes in supply and demand. The maximum price you are willing to pay is not used as a billing basis. Paying a higher price can increase your chances of successfully purchasing a spot ECS. A spot ECS can be used only when the market price is lower than the maximum price you are willing to pay and inventory resources are sufficient. When the market price exceeds the maximum price, the ECS will be reclaimed.

    Billing cycle: A spot ECS is billed by the second. A bill is generated on the hour. The start price of the bill is the market price when the ECS was purchased, and the market price on the hour is used for billing.

    Associated services: Spot pricing applies only to vCPUs and memory. The billing of OSs, system disks, data disks, bandwidth, and IP addresses follows their respective pay-per-use billing rules. A system disk is created and released with the ECS to which the system disk is attached. A data disk must be manually deleted.

    Coupons: Coupons are not applicable to spot ECSs.

Billing Examples

In both pay-per-use and spot pricing billing modes, ECSs are billed by the second. The price per second of each type of ECS can be obtained by dividing their hourly price by 3600. Obtain the hourly price from the ECS product pricing details page.

For example, if you purchase a pay-per-use ECS priced $0.68 USD/hour, the ECS will be billed based on the usage duration by the second.
  • If you use the ECS for 30 minutes, you need to pay for $0.34 USD (0.68/3,600 × 30 × 60).
  • If you use the ECS for 1 hour and 30 minutes, you need to pay for $1.02 USD (0.68/3,600 × 90 × 60).

Configuration Changes

  • Changing the billing mode
    • Changing from pay-per-use to yearly/monthly: After the billing mode of an ECS is changed from pay-per-use to yearly/monthly, a new order is then generated for you, and the new billing mode takes effect immediately after you pay for the order.
    • Changing from yearly/monthly to pay-per-use: After the billing mode is changed from yearly/monthly to pay-per-use, the pay-per-use billing mode takes effect immediately.
    • A spot ECS cannot be changed to a pay-per-use or yearly/monthly ECS.
    Figure 1 ECS billing mode changes
  • Modifying ECS specifications

    For an ECS billed on a yearly/monthly or pay-per-use basis, you can modify its specifications (vCPUs and memory). However, a spot ECS does not support specifications modification.

    Notes

    • Coupons will not be refunded if the specifications of the ECS purchased with those coupons are downgraded.
    • If ECS specifications are upgraded, you need to pay for the price difference between the original and new specifications based on the usage duration.
      • For pay-per-use ECSs, the specification modifications take effect immediately.
      • For yearly/monthly ECSs, the specification modifications take effect immediately within the original subscription term. For details about the price difference, see Pricing of a Changed Specification.
    • Downgrading ECS specifications (vCPU or memory) deteriorates the ECS performance.
    • If a downgraded ECS needs to be upgraded back to its original specifications, the price difference must be paid.

Sitemizi ve deneyiminizi iyileştirmek için çerezleri kullanırız. Sitemizde tarama yapmaya devam ederek çerez politikamızı kabul etmiş olursunuz. Daha fazla bilgi edinin

Feedback

Feedback

Feedback

0/500

Selected Content

Submit selected content with the feedback