Elastic Compute Service:Overview

Item

Reserved instance

Pay-as-you-go instance

Subscription instance

Form

A discount coupon. Reserved instances are classified into regional and zonal reserved instances.

An instance that uses the pay-as-you-go billing method. A pay-as-you-go instance is equivalent to a virtual machine. For more information, see Pay-as-you-go.

An instance that uses the subscription billing method. A subscription instance is equivalent to a virtual machine. For more information, see Subscription.

Purpose

Reserved instances cannot be independently used. They must be matched to pay-as-you-go instances to offset bills.

Pay-as-you-go instances can be independently used. They can be used as simple web servers, or used in combination with other Alibaba Cloud services to deliver powerful solutions.

Subscription instances can be independently used. They can be used as simple web servers, or used in combination with other Alibaba Cloud services to deliver powerful solutions.

Scenario

Combination of reserved instances and pay-as-you-go instances

Pay-as-you-go instance

Subscription instance

You may need to change the region for your business. You must release Elastic Compute Service (ECS) instances in the original zone and create ECS instances in the zones of the destination region.

A combination of reserved instances and pay-as-you-go instances has the following benefits:

• After you purchase reserved instances, you make commitments to using pay-as-you-go instances for a period of time. Reserved instances provide significant discounts compared with pay-as-you-go pricing.

• Purchased reserved instances deliver computing power instead of specific instances. Reserved instances can be matched to eligible pay-as-you-go instances and are more flexible than subscription instances.

• You can split or merge reserved instances to offset the bills of pay-as-you-go instances of different instance types.

• You can modify the zone of a reserved instance anytime. A regional reserved instance can be used to offset the bills of pay-as-you-go instances across zones.

• You can pay by hour by selecting the Partial Upfront or No Upfront payment option to avoid financial pressure caused by one-time payment.

The unit prices of pay-as-you-go instances are higher than those of subscription instances. Pay-as-you-go instances may fail to be created if resources are insufficient. However, pay-as-you-go instances are easier to manage. For example, after you configure automated O&M, instances are automatically created and released. No manual refunds are involved after the instances are released. Pay-as-you-go instances can be used together with Auto Scaling.

Bills are associated with subscription instances. You may need to pay service fees when you apply for refunds.

During automated O&M, the number of subscription instances needs to be automatically adjusted.

Refunds must be manually implemented.

You use Auto Scaling to manage ECS instances and have a large number of pay-as-you-go instances. You want to lower your costs.

You must manually change pay-as-you-go instances to subscription instances. This process is inefficient and prone to errors.

You want to simplify the lifecycle management operations of subscription instances, such as renewing, releasing, and synchronizing the expiration dates of subscription instances.

You must perform a large number of operations.

You want to pay for resources by installments to mitigate financial pressure.

The unit prices are lower. However, one-time payment is required.

Section

Attribute

Description

①

Instance types

The following instance families support reserved instances:

• General-purpose instance families: g8a, g7, g7a, g6e, g6, g5, g5ne, and sn2ne

• Compute-optimized instance families: c8a, c7, c7a, c6e, c6, c5, ic5, and sn1ne

• Memory-optimized instance families: r8a, r7, r7a, r6e, r6, r5, re6, re4, and se1ne

• Big data instance family: d2s

• Instance families with local SSDs: i3, i3g, i2, i2g, and i2gne

• Instance families with high clock speeds: hfg7, hfc7, hfr7, hfg6, hfc6, hfr6, hfg5, and hfc5

• GPU-accelerated compute-optimized instance families: gn7, gn6i, gn6e, gn6v, gn5, and gn5i

• ECS Bare Metal Instance families: ebmgn7, ebmgn6i, ebmgn6e, ebmg6, ebmc6, ebmr6, ebmhfg6, ebmhfc6, and ebmhfr6

• Burstable instance families: t6 and t5

②

Region and zone

For a regional reserved instance, you need only to specify a region. Regional reserved instances provide zone flexibility and instance size flexibility. For a zonal reserved instance, you must specify a region and a zone. Zonal reserved instances provide resource reservation. The matching conditions are determined by the type of a reserved instance. For more information, see Match between reserved instances and pay-as-you-go instances.

After you purchase a reserved instance, you can modify its region and zone as needed. For more information, see Change the name or zone of a reserved instance.

③

Operating system

Reserved instances are classified into Linux and Windows reserved instances. Windows reserved instances can be used to offset the image bills of Windows pay-as-you-go instances.

④

Normalization factor

A normalization factor indicates the performance level of an instance type and also the computing power. Normalization factors are determined by the number of vCPUs. For information about detailed specifications, see View normalization factors.

⑤

Instance quantity

The instance quantity is used for the following purposes:

• Calculates the computing power of reserved instances.

• Specifies the number of reserved resources for zonal reserved instances. For example, in the preceding figure, the instance quantity is two and the instance type in use is ecs.r6e.xlarge. This indicates that two pay-as-you-go instances of the ecs.r6e.xlarge instance type are reserved.

⑥

Computing power

Reserved instances deliver computing power in advance. Pay-as-you-go instances consume the computing power. Computing power of a reserved instance = Normalization factor of an instance type × Instance quantity.

⑦

Term

You must specify the term when you purchase a reserved instance. After you split, merge, and modify reserved instances, the terms of the original and new reserved instances are also changed. For more information, see Split a reserved instance, Merge reserved instances, and Change the name or zone of a reserved instance.

A reserved instance takes effect and expires on the hour. For example, assume that you purchase a reserved instance with a term of one year at 13:45:00 of May 29, 2020. The reserved instance takes effect at 13:00:00 of May 29, 2020 and expires at 24:00:00 of May 30, 2021. If you have pay-as-you-go instances that match the reserved instance, the reserved instance is applied to offset the bills of the matching pay-as-you-go instances from 13:00:00 of May 29, 2020 by hour until it expires.