Reserved Instance Overview
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.
- 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.
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. |
- For instructions about how to purchase an RI, see Enabling and Purchasing a Reserved Instance.
- For instructions about how to modify an RI, see Modifying RI Attributes.
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.
Parameter |
Description |
---|---|
Region or AZ |
|
Flavor |
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
- 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.
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.
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
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.
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