Halaman ini belum tersedia dalam bahasa lokal Anda. Kami berusaha keras untuk menambahkan lebih banyak versi bahasa. Terima kasih atas dukungan Anda.

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

Reserved Instance Overview

Updated on 2024-10-18 GMT+08:00

Concept

A reserved instance (RI) is not an actual instance, but a billing discount that can be applied to the use of pay-per-use ECSs in your account. When the attributes of your pay-per-use ECSs match those of an RI, the RI billing benefit automatically applies to your ECSs. The combination of RIs and pay-per-use billing fully utilizes the flexibility of pay-per-use resources at lower costs.

NOTE:
  • A purchased RI is billed, regardless of whether it is used or not.
  • RIs cannot be used on the ECSs running Microsoft SQL Server.
  • RIs are in the open beta test (OBT) phase. You can apply for OBT.
Table 1 ECS billing modes

Billing Mode

What It Is

How to Use

RI

A billing discount applied to pay-per-use ECSs.

When the attributes of your pay-per-use ECSs match those of an RI, the RI billing benefit automatically applies to your ECSs.

Pay-per-use

ECS billed based on usage frequency and duration. Such an ECS can be created or deleted at any time.

A basic computing unit that consists of vCPUs, memory, OS, and EVS disks. After purchasing such an ECS, you can use it on the cloud.

Yearly/Monthly

ECS billed based on the service duration. This mode is ideal when the duration of ECS usage is predictable.

A basic computing unit that consists of vCPUs, memory, OS, and EVS disks. After purchasing such an ECS, you can use it on the cloud.

Spot pricing

ECS billed in spot pricing billing mode.

A basic computing unit that consists of vCPUs, memory, OS, and EVS disks. After purchasing such an ECS, you can use it on the cloud.

What Is Attribute Mapping Between an RI and a Pay-per-Use ECS?

A regional RI is purchased within a region and without an AZ specified. A zonal RI is purchased within an AZ.

  • Attribute mapping of a regional RI: indicates whether the region, OS type, ECS series, and vCPU/memory ratio of a pay-per-use ECS are the same as those specified in a regional RI.
  • Attribute mapping of a zonal RI: indicates whether the AZ, OS type, flavor of a pay-per-use ECS are the same as those specified in a zonal RI.

Application Scenarios

If your ECSs are to be used in a short term, it is a good practice to use the pay-per-use billing mode. If you plan to use ECSs for one or three years, it is a good practice to use RIs. RIs offer discounts for pay-per-use ECSs with matched attributes.

For example, after you purchase two s3.2xlarge Linux RIs with a one-year term in AZ 1, the billing benefit of the RIs is immediately applied to up to two pay-per-use s3.2xlarge Linux ECSs running in AZ 1.

Working Rules

For example, you have a running pay-per-use ECS in your account. After you purchase an RI that matches the attributes of this ECS, the billing benefit of the RI is automatically applied to your ECS when the RI takes effect. A purchased RI takes effect at the next hour.

Table 2 lists RI attributes. You can purchase your desired RIs based on these attributes.

Table 2 RI attributes

Parameter

Description

Region or AZ

  • Regional RI: indicates an RI purchased in a region, without an AZ specified. Capacity reservations are not supported for regional RIs.
  • Zonal RI: indicates an RI purchased with an AZ specified. Capacity reservations are supported for zonal RIs.

Flavor

  • When purchasing a regional RI, ensure that the ECS series and vCPU/memory ratio specified in the RI are the same as those of the target pay-per-use ECS.
  • When purchasing a zonal ECS, ensure that the flavor specified in the RI is the same as that of the target pay-per-use ECS.
NOTE:

After an RI is purchased, its flavor cannot be directly changed, but you can split or combine it. For details, see Modifying RI Attributes.

OS

The OS of the ECS to be bought, which must match the OS specified in your RI. For example, if you want to use a Linux RI, select a Linux public or private image when purchasing an ECS.

Term

The service duration of an RI. A year is defined as 31,536,000 seconds (365 days).

Offering Class

Standard: Certain attributes, such as the ECS size can be modified during the term. However, the ECS type cannot be changed.

Payment Option

No upfront

Zonal RIs

A zonal RI, which is purchased within a specified AZ, offers a billing discount for the ECSs with the same OS and flavor as the RI in that AZ.

For example, after you purchase two c3.xlarge.2 Linux RIs with a one-year term in AZ 1, the billing benefit of the RIs is immediately applied to up to two pay-per-use c3.xlarge.2 Linux ECSs running in AZ 1.

Regional RIs

A regional RI, which is purchased within a specified region, has the following characteristics:
  • AZ flexibility: The RI discount applies to pay-per-use ECS usage in any AZ within a region.
  • ECS size flexibility: The RI discount applies to pay-per-use ECS usage when the ECS OS, ECS series, and vCPU/memory ratio of the target ECS are the same as those specified in the regional RI. ECS size flexibility is determined based on the normalization factor of the ECS size. ECS size flexibility does not apply to zonal RIs.

ECS size flexibility is applied from the smallest to the largest ECS size within the ECS series based on the normalization factor. Table 3 describes ECS size within an ECS type and corresponding normalization factor per hour.

NOTE:

An ECS automatically benefits from the billing discount offered by a regional RI only when the ECS series and vCPU/memory ratio are the same as those specified in the RI.

For example, a regional c3.large.4 RI cannot be used on a c3.large.2 ECS because their vCPU/memory ratios are different.

Table 3 Normalization factors

ECS Size

Normalization Factor

small

1

medium

1

large

2

xlarge

4

2xlarge

8

4xlarge

16

6xlarge

24

7xlarge

28

8xlarge

32

9xlarge

36

12xlarge

48

14xlarge

56

15xlarge

60

16xlarge

64

26xlarge

104

52xlarge

208

nxlarge

n x 4

For example, an s3.large.2 ECS has a normalization factor of 2. You purchase an s3.large.2 Linux RI for the CN-Hong Kong region of Huawei Cloud with a one-year term.

  • If you have two running s3.medium.2 pay-per-use Linux ECSs in this region, the billing benefit is fully applied to both ECSs.
    Figure 1 Example RI 1
  • If you have one running s3.xlarge.2 pay-per-use Linux ECS with a normalization factor of 4 in this region, the billing benefit is applied to 50% of the usage of the ECS.
    Figure 2 Example RI 2
Table 4 Comparison between regional and zonal RIs

RI Type

AZ Flexibility

ECS Size Flexibility

Capacity Reservation

Regional RI

Supported

A regional RI applies to any AZ in the region.

Supported

A regional RI applies when the ECS series and vCPU/memory ratio of the target ECS are the same as those specified in the RI.

Not supported

Resources are not reserved so ECS creation may fail when resources are insufficient.

Zonal RI

Not supported

A zonal RI applies only in a specified AZ.

Not supported

A zonal RI applies only when the flavor of the target ECS is the same as that specified in the RI.

Supported

Desired resources can be reserved for creating a pay-per-use ECS.

Examples

If you have the following pay-per-use ECSs in region A:

  • Five s3.large.2 Windows ECSs in AZ 1
  • Three m3.xlarge.2 Windows ECSs in AZ 2
  • One c3.xlarge.2 Windows ECS in AZ 3

You purchase the following RIs in the same region (region A):

  • Five s3.large.2 Windows RIs with a one-year term in AZ 1
  • Six m3.large.2 Windows RIs with a one-year term in region A
  • One c3.large.2 Windows RI with a one-year term in region A

The RI benefits are applied as follows:

  • The discount of the five s3.large.2 zonal RIs is used by the five s3.large.2 ECSs because the attributes (AZ, OS, and ECS type) between the RIs and ECSs match.
  • The m3.large.2 regional RIs offer AZ flexibility and ECS size flexibility.

    An m3.large.2 RI is equivalent to two normalization factors. The six m3.large.2 regional RIs are equal to 12 normalization factors (6 x 2). There are three running m3.xlarge.2 ECSs in your account, which are equivalent to 12 normalization factors (3 x 4). In this case, the six m3.large.2 regional RIs are equivalent to three m3.xlarge.2 ECSs.

  • The c3.large.2 regional RI offers AZ flexibility and ECS size flexibility and can be applied to c3.xlarge.2 ECSs.

    A c3.large.2 RI is equivalent to two normalization factors (1 x 2). A c3.xlarge.2 ECS requires an RI with four normalization factors (1 x 4). Therefore, the c3.large.2 RI billing discount applies to 50% of c3.xlarge.2 usage. The remaining c3.xlarge.2 usage is billed at the pay-per-use rate.

Kami menggunakan cookie untuk meningkatkan kualitas situs kami dan pengalaman Anda. Dengan melanjutkan penelusuran di situs kami berarti Anda menerima kebijakan cookie kami. Cari tahu selengkapnya

Feedback

Feedback

Feedback

0/500

Selected Content

Submit selected content with the feedback