If your business areas change, you can change the names or scopes (regions or zones) of your reserved instances to better match pay-as-you-go instances. This topic describes how to change the name or zone of a reserved instance.
Prerequisites
In this topic, the reserved instance whose name or scope you want to change is called original reserved instance, and the reserved instance that is generated during the change is called new reserved instance.
The original reserved instance is in the Active state.
The original reserved instance is not being split, merged, or modified.
Background information
If you want to change the scope of a reserved instance, you can perform the following operations:
Change the scope from a zone in a region to the region.
Change the scope from a region to a zone in the region.
Change the scope from a zone to another zone in the same region.
Example 1: The scopes of reserved instances are successfully changed
The following figure shows reserved instances whose scopes are successfully changed.
Example 2: The scopes of reserved instances fail to be changed across regions
You cannot change the scopes of reserved instances across regions. The following figure shows reserved instances whose scopes fail to be changed across regions.
Procedure
Log on to the ECS console.
In the left-side navigation pane, choose Deployment & Elasticity >
> Reserved Instances. On the Reserved Instances page, find the reserved instance whose name or scope you want to change 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.
NoteIf resources for the instance type used by the reserved instance are insufficient in a zone, you cannot select the zone for the reserved instance.
Click OK.
Result
After you submit the change request, the original reserved instance enters the Updating state, and a new reserved instance in the Creating state appears in the reserved instances list. You cannot cancel a change request that is being processed. To undo the changes to the original reserved instance, change the name and the scope of the reserved instance to the original values.
After the change request is processed, you can obtain one of the following results:
If the change is complete, the following situations occur:
The original reserved instance enters the Inactive state and is invalidated on the hour when the reserved instance is changed. The price of the original reserved instance becomes USD 0.
The new reserved instance enters the Active state and takes effect on the hour when the original reserved instance is changed. If the new reserved instance is a zonal reserved instance, the zone in which resources are reserved is automatically updated.
If the new reserved instance matches pay-as-you-go instances, the billing discount provided by the reserved instance is applied to the matched pay-as-you-go instances starting from the hour when the reserved instance takes effect.
If the change fails, the original reserved instance is unchanged and remains in the Active state.
For example, you change a zonal reserved instance that reserves resources into a regional reserved instance that does not reserve resources at 10:50:00 on June 20, 2024. The following figure shows the time when the original reserved instance is invalidated and the time when the new reserved instance takes effect.
