このページは、お客様の言語ではご利用いただけません。Huawei Cloudは、より多くの言語バージョンを追加するために懸命に取り組んでいます。ご協力ありがとうございました。

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

Pay-per-Use Billing

Updated on 2023-12-01 GMT+08:00

Pay-per-use billing means you pay nothing up front and are not tied into any contract or commitment. This section describes the billing rules for pay-per-use load balancers.

Application Scenarios

Pay-per-use is suitable for applications or services that cannot be interrupted when facing temporary or sudden traffic increases or unpredictable demands, such as e-commerce flash sales, testing, and scientific computing.

Billing Items

Table 1 lists the billing items of pay-per-use load balancers.

Table 1 Billing items

Load Balancer Type

Specifications

LCU

Load Balancer

Dedicated

Elastic

Fixed

×

Shared

Fixed

×

If you purchase a dedicated load balancer with fixed specifications, deploy it in two AZs, and select small I for both application load balancing (HTTP/HTTPS) and network load balancing (TCP/UDP), the prices are as shown in the following figure.

Figure 1 Example prices

You are charged for:

  • Network load balancing: 20 LCUs (10 LCUs for each AZ).
  • Application load balancing: 20 LCUs (10 LCUs for each AZ).
NOTE:
  • If you deploy a dedicated load balancer in multiple AZs, its performance will multiply as the number of AZs increases. The number of LCUs is calculated as follows: Number of LCUs = LCUs of the selected specification x Number of the selected AZs.
  • If you bind an EIP to this load balancer, you will also be charged for the EIP and the bandwidth used by the EIP. For details about EIP pricing, see Elastic IP Pricing Details.

Billed Usage Period

Pay-per-use load balancer usage is calculated by the second and billed every hour. The billing starts when the load balancer is created and ends when it is deleted.

NOTE:

The billing starts from the creation time on the load balancer Summary page.

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

Billing Examples

Suppose you purchased a pay-per-use load balancer with fixed specifications at 9:30:00 on April 18, 2023, deployed it in one AZ, and selected small I for both application load balancing (HTTP/HTTPS) and network load balancing (TCP/UDP). Later you upgraded small I to small II for application load balancing at 10:00:00 on April 19, 2023 and deleted the load balancer at 12:00:00 on April 19, 2023.

The total price you need to pay is calculated as shown in the below table.

Table 2 Billing details of the load balancer

Billing Item

Required Duration

Pricing Details (USD)

Total Price (USD)

Network load balancing

(10 LCUs)

  • 2023/04/18 9:30:00 – 2023/04/19 00:00:00

    870 minutes

  • 2023/04/19 00:00:00 – 2023/04/19 12:00:00

    720 minutes

  • 870/60 x 0.07 = 1.015
  • 720/60 x 0.07 = 0.84

1.015 + 0.84 = 1.855

Application load balancing

(10 LCUs)

  • 2023/04/18 9:30:00 – 2023/04/19 00:00:00

    870 minutes

  • 2023/04/19 00:00:00 – 2023/04/19 10:00:00

    600 minutes

  • 870/60 x 0.07 = 1.015
  • 600/60 x 0.07 = 0.7

1.015 + 0.7 = 1.715

Application load balancing

(20 LCUs)

2023/04/19 10:00:00 – 2023/04/19 12:00:00

120 minutes

(120/60) x 0.14= 0.28

0.28

Figure 2 shows how the total price is calculated.

Figure 2 Total price for a pay-per-use dedicated load balancer
NOTICE:

The prices in the figure are for reference only. The actual calculation is subject to the prices in the ELB Pricing Details.

Price Change After Specification Change

If you change the specifications of a pay-per-use load balancer, 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 specifications within a given hour, multiple records will be generated. Different records record the billing for different specifications.

Assume that you purchased a pay-per-use load balancer at 9:00:00, deployed it in two AZs, and selected small I for both application load balancing and network load balancing. Later you upgraded small I to small II for both application load balancing and network load balancing. The following items are billed:

  • Usage of application load balancing (HTTP/HTTPS) – small I and network load balancing (TCP/UDP) – small I from 9:00:00 to 9:30:00
  • Usage of application load balancing (HTTP/HTTPS) – small II and network load balancing (TCP/UDP) – small II from 9:30:00 to 10:00:00

Impact of Arrears

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

Figure 3 Lifecycle of a pay-per-use load balancer

Arrears Reminder

The system will bill you for pay-per-use load balancers after each billing cycle ends. If your account goes into arrears, we will notify you by email, SMS, or in-app message.

Impacts of Arrears

If your account is insufficient to pay your amount due, your account goes into arrears, and pay-per-use load balancers enter the grace period. You are still responsible for expenditures generated during the grace period. You can view the charges on the Billing & Costs > Billing Center > Overview page and pay any past due balance as needed.

If your account is still in arrears after the grace period ends, your load balancers enter the retention period and their status turns to Frozen. You cannot perform any operations on them.

After the retention period ends, your load balancers will be released and data cannot be restored.

NOTE:

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