Your workloads may change. For example, you may want your workloads to be dispersed across low-specification instances or concentrated on a few high-specification instances, or you may want to extend the capacity of instances across zones. To adapt to workload changes, you can split, merge, or modify existing reserved instances to match pay-as-you-go instances of different specifications and zones. This ensures that you can continue to use discounts and meet computing resource requirements in the changed scenarios. This allows you to efficiently manage and optimize the costs and usage efficiency of your cloud resources.
In this topic, the source reserved instances are the reserved instances to be split, merged, or modified, and the destination reserved instances are obtained after the source reserved instances were split, merged, or modified.
Prerequisites
Before you split, merge, or modify reserved instances, take note of the following items:
The source reserved instances are in the Active state.
The source reserved instances are not being split, merged, or modified.
If you want to merge reserved instances, take note of the following items:
The source regional reserved instances reside in the same region.
The source zonal reserved instances reside in the same zone.
The source reserved instances have the same operating system and end time.
NoteThe end time of a reserved instance is determined when you purchase the reserved instance, and is not necessarily the time when the reserved instance becomes inactive. For example, after you merge the reserved instances, the source reserved instances become inactive. However, the end time of the source reserved instances remains unchanged.
Split a reserved instance
When your workloads are distributed across lower-specification pay-as-you-go instances, you can split a reserved instance into multiple reserved instances with lower computing power to better match the lower-specification pay-as-you-go instances and cope with the resulting traffic diversion.
Limits
When you split a reserved instance, take note of the following items:
Reserved instances that belong to the gn6i and t5 instance families cannot be split.
You can change the instance type of a reserved instance. However, you cannot change the instance family of a reserved instance.
You cannot change the zone or region of a reserved instance.
The sum of the computing power of the destination reserved instances must be equal to the computing power of the source reserved instance.
NoteComputing power of a reserved instance = Normalization factor of the instance type × Number of instances that can be offset by a reserved instance. For more information about how to view the normalization factors of different instance types, see View the normalization factor table.
Procedure
Go to the Reserved Instances page.
Log on to the ECS console.
In the left-side navigation pane, choose Deployment & Elasticity >
> Reserved Instances. In the top navigation bar, select the region and resource group to which the resource belongs.
On the Reserved Instances page, find the source reserved instance and click Split in the Actions column.
In the Split Reserved Instance pane, configure the names, instance types, and quantities of the destination reserved instances.
Click OK.
For information about operation results, see the Operation results section of this topic.
Merge reserved instances
If your workloads are concentrated on a few high-specification instances, you can combine multiple reserved instances into one reserved instance to provide higher computing power to match higher-specification pay-as-you-go instances.
Limits
When you merge reserved instances, take note of the following items:
Reserved instances that belong to the gn6i and t5 instance families cannot be merged.
You can change the instance type of a reserved instance. However, you cannot change the instance family of a reserved instance.
You cannot change the zone or region of a reserved instance.
The number of pay-as-you-go instances to which the destination reserved instance can be applied cannot exceed 100.
The sum of the computing power of the destination reserved instances must be equal to the computing power of the source reserved instance.
NoteComputing power of a reserved instance = Normalization factor of the instance type × Number of instances that can be offset by a reserved instance. For more information about how to view the normalization factors of different instance types, see the View the normalization factor table section of the "View reserved instances" topic.
Procedure
Go to the Reserved Instances page.
Log on to the ECS console.
In the left-side navigation pane, choose Deployment & Elasticity >
> Reserved Instances. In the top navigation bar, select the region and resource group to which the resource belongs.
On the Reserved Instances page, find a source reserved instance that you want to merge and click Merge in the Actions column.
In the Merge Reserved Instances pane, select the reserved instances that you want to merge with the current reserved instance. Then, configure the name, instance type, and quantity of the destination reserved instance.
Click OK.
For information about operation results, see the Operation results section of this topic.
Change the zone of a reserved instance
If a source reserved instance is no longer applicable to the new region or zone due to business expansion or migration, you can change the zone of the reserved instance to better match pay-as-you-go instances.
Go to the Reserved Instances page.
Log on to the ECS console.
In the left-side navigation pane, choose Deployment & Elasticity >
> Reserved Instances. In the top navigation bar, select the region and resource group to which the resource belongs.
On the Reserved Instances page, find the reserved instance that you want to manage and click Modify in the Actions column.
In the Modify Reserved Instance panel, specify a new name and select a different zone from the Region/Zone drop-down list.
You can change the zone in the Region/Zone field only to a different zone in the same region.
For a zonal reserved instance:
You can change the zone to another zone in the same region.
You can change a zonal reserved instance to a regional reserved instance.
For a regional reserved instance, you can change the instance to a zonal reserved instance in the same region.
NoteIf resources for the instance type used by the destination reserved instance are insufficient in a zone, you cannot select the zone for the reserved instance.
Click OK.
For information about operation results, see the Operation results section of this topic.
Operation results
After you submit the request to split, merge, or modify reserved instances, the source reserved instances enter the Updating state, and the destination reserved instances in the Creating state are displayed.
You cannot cancel a request that is in progress. If you want to undo a change, you must split, merge, or modify the reserved instances again. For example, to undo the split operation, you can merge the destination reserved instances back into the source reserved instance.
After the split, merge, or modify request is processed, take note of the following billing considerations:
If the reserved instances are split, merged, or modified as expected, the following situations occur:
Source reserved instances
The source reserved instances enter the Inactive state and are invalidated on the hour when the source reserved instance configuration was changed. The price of the source reserved instances becomes USD 0.
For source reserved instances, you can only view historical bills.
Destination reserved instances
The destination reserved instances enter the Active state and take effect on the hour when the source reserved instances are split, merged, or modified.
Assume that you split an ecs.g6.2xlarge zonal reserved instance into two ecs.g6.xlarge zonal reserved instances at 20:30 on May 28, 2020. The source reserved instance is invalidated at 20:00 on May 28, 2020, the same time as when the destination reserved instances take effect.
If the destination reserved instance is a zonal reserved instance, the type of reserved resources is updated automatically.
If the destination reserved instance matches pay-as-you-go instances, the billing discount provided by the reserved instance is applied to the matching pay-as-you-go instances starting from the hour when the destination reserved instance takes effect.
If the configuration modification fails, the source reserved instance is unchanged and remains in the Active state.