Which instance types support resizing?-Elastic Compute Service(ECS)-阿里云帮助中心

This topic explains what to check before changing an instance type and how to resolve common issues.

Instance type change pre-checks

1. Check instance type compatibility

First, confirm that your current instance type can be changed and is compatible with the target instance type.

Confirm that the current instance type is not in the list of instance types that do not support changes.
In the list of instance types available for a change, find the instance family of the current instance and confirm that the target instance family is supported.

You can also call the DescribeResourcesModification API to query the list of target instance types that are supported for the current instance.

2. Check operating system compatibility

Some instance types, especially those based on different CPU architectures such as AMD, Intel, and Yitian, have specific operating system requirements. If the operating system of the current instance is not compatible with the target instance type, the change will fail.

Use the following lists to verify that your operating system is compatible with the target instance type.

If the operating system is not compatible but you still need to change the instance type, you can request to lift the restriction.

How to lift the restriction

Important

Lifting this restriction applies to all regions and is irreversible.

On the Custom Launch page of the ECS console, set Image Type to Custom Images, and then click the Check Operation link.
After reviewing the associated risks, select the checkbox to lift the restriction, and then click OK. Wait for about one minute for the change to take effect.

3. Check NVMe driver compatibility

ECS instances of the 8th generation and later, such as g8i, c8i, r8i, u2i, g8a, c8a, r8a, and u2a, use the NVMe protocol to communicate with disks. These instances require an NVMe driver. You must check the NVMe driver in the following scenarios:

Scenario 1: Change from a 7th-generation or earlier instance type to an 8th-generation or later instance type

The source ECS instance must either have the NVMe driver installed or use an image that supports its installation.
Scenario 2: The source instance is an 8th-generation or later instance type

The source instance must already have the NVMe driver installed.

You can determine the generation of an instance type from its family name. For more information, see Instance type naming conventions.

How to check and install the NVMe driver

In the Instances page of the ECS console, find the instance, and then choose > Configure NVMe Driver Status.
If the NVMe driver is installed, the status is Installed.
If the driver is not installed, click Install. The system automatically installs the NVMe driver and updates the status to Installed.

Related API operations

To query whether an instance type supports NVMe, call DescribeInstanceTypes. If NVMe is supported, the value of NvmeSupport is required.
To query whether an image supports NVMe, call DescribeImages. If NVMe is supported, the value of NvmeSupport is supported.

4. Check disk type compatibility

Different instance types support different disk types. For example, the g7 instance family supports only ESSD-series disks. If your instance uses a disk type that is not supported by the target instance type, you cannot change the instance type.

On the change instance type page, the system automatically detects disk compatibility issues and prompts you to change the disk type accordingly. Review the prompts and the associated cost changes, as shown in the following figure.

Supported instance types

You can change a source instance type to a target instance type listed in the following tables.

Note

Call the DescribeResourcesModification API operation to query supported instance type changes for an instance.

Table 1. entry-level x86 compute-optimized instance families

Source instance family	Target instance families
e	g7, c7, r7, g7ne, g7nex, c7nex, hfg7, hfc7, hfr7 g6, c6, r6, g6e, c6e, r6e, hfg6, hfc6, hfr6, re6 u1 e t6, s6
t6, s6	g7, c7, r7, hfg7, hfc7, hfr7, g7ne g6, c6, r6, hfg6, hfc6, hfr6, g6e, c6e, r6e, re6 t6, s6
t5	g6, c6, r6, hfc6, hfg6, hfr6, g6a, c6a, r6a, re6 g5, g5ne, r5, c5, ic5, hfc5, hfg5 t5, t6, s6
n4, mn4, xn4, e4	g6, c6, r6, hfc6, hfg6, hfr6, g6a, c6a, r6a, re6 g5, g5ne, r5, c5, ic5, hfc5, hfg5 t5, t6, s6 se1, sn1ne, sn2ne, se1ne, c4, ce4, cm4, re4, n4, mn4, xn4, e4
t1, s1, s2, s3, m1, m2, c1, c2	g5, g5ne, r5, c5, ic5, hfc5, hfg5 t5 se1, sn1ne, sn2ne, se1ne, c4, ce4, cm4, re4, n4, mn4, xn4, e4
n1, n2, e3	g5, g5ne, r5, c5, ic5, hfc5, hfg5 t5 se1, sn1ne, sn2ne, se1ne, c4, ce4, cm4, re4, n4, mn4, xn4, e4

Table 2. enterprise-level compute-optimized instance families

Source instance	Target instance families
g9a, c9a, r9a, g9ae, c9ae, r9ae, u2a	g9a, c9a, r9a, g9ae, c9ae, r9ae, u2a
g9i, c9i, r9i, hfg9i, hfc9i, hfr9i	g9i, c9i, r9i, hfg9i, hfc9i, hfr9i, u2i
g8i, c8i, r8i hfg8i, hfc8i, hfr8i	g9i, c9i, r9i, hfg9i, hfc9i, hfr9i, u2i g8i, c8i, r8i, hfg8i, hfc8i, hfr8i, g8ise
g8ise	g8i, c8i, r8i, hfg8i, hfc8i, hfr8i, g8ise
g8a, c8a, r8a g8ae, c8ae, r8ae	g9a, c9a, r9a, g9ae, c9ae, r9ae, u2a g8a, c8a, r8a, g8ae, c8ae, r8ae
g8y, c8y, r8y	g8y, c8y, r8y
g7se, c7se, r7se	g8i, c8i, r8i g7se, c7se, r7se
g7a, c7a, r7a	g9a, c9a, r9a, g9ae, c9ae, r9ae, u2a g8a, c8a, r8a, g8ae, c8ae, r8ae g7a, c7a, r7a, g7, c7, r7 g6a, c6a, r6a
ebmg7a, ebmc7a, ebmr7a	ebmg7a, ebmc7a, ebmr7a
ebmhfc7, ebmhfg7, ebmhfr7	ebmhfc7, ebmhfg7, ebmhfr7
g7, c7, r7	g9i, c9i, r9i u2i g8i, c8i, r8i, hfg8i, hfc8i, hfr8i, g8ise g7, c7, r7, g7ne, g7nex, c7nex, hfc7, hfg7, hfr7
ebmg7, ebmc7, ebmr7	ebmg7, ebmc7, ebmr7
g7ne hfc7, hfg7, hfr7 g6e, c6e, r6e	g9i, c9i, r9i, hfg9i, hfc9i, hfr9i g8i, c8i, r8i, hfg8i, hfc8i, hfr8i, g8ise g7, c7, r7, g7ne, g7nex, c7nex, hfc7, hfg7, hfr7 g6e, c6e, r6e
g7nex, c7nex	g8i, c8i, r8i, hfg8i, hfc8i, hfr8i, g8ise g7, c7, r7, g7ne, g7nex, c7nex, hfc7, hfg7, hfr7 Important ecs.g7nex.32xlarge can only be changed to ecs.c7nex.32xlarge.
g7h	g7h
g6h	g6h
g6r, c6r	g8y, c8y, r8y g6r, c6r
g6, c6, r6 hfg6, hfc6, hfr6	g7, c7, r7, hfg7, hfc7, hfr7, g7ne g6, c6, r6, hfg6, hfc6, hfr6, g6e, c6e, r6e, re6 t6, s6
g6a, c6a, r6a	g9a, c9a, r9a, g9ae, c9ae, r9ae, u2a g8a, c8a, r8a, g8ae, c8ae, r8ae g7, c7, r7, g7a, c7a, r7a g6, c6, r6, g6a, c6a, r6a
g6t	g6t
c6t	c6t
ebmg6a, ebmc6a, ebmr6a	ebmg6a, ebmc6a, ebmr6a
g5, g5ne, r5, c5, ic5	g7, c7, r7 g6, c6, r6, g6a, c6a, r6a, hfc6, hfg6, hfr6, re6 g5, g5ne, r5, c5, ic5, hfc5, hfg5, ebmg5s t5, t6, s6
hfc5, hfg5	g7, c7, r7 g6, c6, r6, g6a, c6a, r6a, hfc6, hfg6, hfr6, re6 u1 hfc5, hfg5, g5, g5ne, r5, c5, ic5, t5 e t6, s6
u2i	u2i
u1	g7, c7, r7, hfg7, hfc7, hfr7 u1, u2i, u2a
sn1ne, sn2ne, se1ne	g6, c6, r6, g6a, c6a, r6a, hfc6, hfg6, hfr6, re6 g5, g5ne, r5, c5, ic5, hfc5, hfg5 e t5, t6, s6 sn1ne, sn2ne, se1ne, re4, n4, mn4, xn4, e4
se1	g7, c7, r7 u1 g5, g5ne, r5, c5, ic5, hfc5, hfg5 t5 se1, sn1ne, sn2ne, se1ne, c4, ce4, cm4, re4, n4, mn4, xn4, e4
re6	g6, c6, r6, hfc6, hfg6, hfr6, re6, ebmre6-6t re4, re4e
re4e	g7, c7, r7 u1 re6, ebmre6-6t re4e, re4
re4	g7, c7, r7 u1 g6, c6, r6, g6a, c6a, r6a, hfg6, hfc6, hfr6, re6, ebmre6-6t e g5, g5ne, r5, c5, ic5, hfc5, hfg5 t5, t6, s6 se1, sn1ne, sn2ne, se1ne, c4, ce4, cm4, re4, n4, mn4, xn4, e4
gn8v	gn8v
gn8v-tee	gn8v-tee
sgn8ia	sgn8ia
gn8is	gn8is
sgn7i-vws	sgn7i-vws
vgn7i-vws	vgn7i-vws
gn7e	gn7e
gn7r	gn7r
gn7s	gn7s
gn7i	gn7i
gn7	gn7
gn6i	gn6i
vgn6i	vgn6i, vgn6i-vws, sgn7i-vws
vgn6i-vws	vgn6i-vws
gn6e	gn6e
gn6v	gn6v
gn5i	gn5i
sn1, sn2, se1	g7, c7, r7 u1 g5, g5ne, r5, c5, ic5, hfc5, hfg5 t5 se1, sn1ne, sn2ne, se1ne, c4, ce4, cm4, re4, n4, mn4, xn4, e4
c4, ce4, cm4	g6, c6, r6, g6a, c6a, r6a, hfc6, hfg6, hfr6, re6 e g5, g5ne, r5, c5, ic5, hfc5, hfg5 t5, t6, s6 se1, sn1ne, sn2ne, se1ne, c4, ce4, cm4, re4, n4, mn4, xn4, e4

Unsupported instance types for specification modification

Important

In the ECS console, the action button for modifying specifications is disabled and a prompt appears for instances that do not support this operation.

You cannot modify the instance specification for instance types that belong to the following instance families:

Family type	Instance family
enterprise-level x86 compute-optimized	RDMA-enhanced: c7re persistent memory-optimized: re6p, re6p-redis, re7p, r7p security-enhanced: g7t, c7t, r7t big data: d3s, d3c, d2c, d2s, d1, d1ne local SSD: i1, i2, i2g, i2ne, i2gne, i3, i3g, i4, i4g, i4r, i4p, i5g, i5ge, i5, i5e
Enterprise-level heterogeneous computing	GPU compute: gn5 GPU virtualization: vgn5i Heterogeneous service: video-trans FPGA compute: f1, f3
ECS Bare Metal Instance	ebmgn8v, ebmgn8is, ebmgn7ex, ebmgn7e, ebmgn7i, ebmgn7ix, ebmgn7, ebmgn6ia, ebmgn6e, ebmgn6v, ebmgn6i ebmg8i, ebmc8i, ebmg8y, ebmc8y, ebmr8y, ebmg6, ebmg5s, ebmg5, ebmc6me, ebmc6, ebmc5s, ebmc4, ebmre6p, ebmre6-6t, ebmr6, ebmr5s ebmi2g ebmhfg6, ebmhfg5, ebmhfc6, ebmhfr6
high-performance computing (HPC) & Super Computing Cluster (SCC)	Super Computing Cluster (SCC) sccgn7ex, sccgn6e, sccgn6 sccg7, sccc7, sccg5, scch5 scchfg6, scchfc6, scchfr6 HPC-optimized: hpc8i, hpc8ae, hpc7ip, hpc6id

FAQ

If you encounter problems when changing an instance type, see the solutions below.

Issue	Description	Solution
Instance type not found	The selected instance type does not exist.	Select another target instance type. For more information, see Available instance families.
Instance type is retired	The selected instance type is retired.	Select another target instance type. For more information, see Available instance families.
Out of stock in the region	The selected target instance type is out of stock in the current region.	Select another instance type that is in stock, or change the instance type across zones (only changes within the same instance family are supported). View available regions for an instance type Query the inventory of an instance type in a specific zone using the API.
Changes only supported within the same instance family	These instances can only be changed to a type within the same instance family.	Select a target instance type that is in the same instance family as the source instance. For example, when you change a gn7e instance type, you can select only an instance type from the gn7e instance family.
Instance family mismatch	The source and target instance families are incompatible.	Refer to Supported instance type changes and select a target instance type that is in a compatible instance family.
Architecture mismatch	The architecture of the target instance (for example, ARM or x86) does not match that of the source instance.	Select a target instance type that has the same architecture as the source instance.
Unsupported CPU core count or memory size	The change is not supported because the operating system of the source instance does not support the CPU core count or memory size of the target instance type. For information about the limits on the number of CPU cores and memory size for Windows, see Memory Limits for Windows and Windows Server Releases.	Select a target instance type with a supported CPU core count or memory size.
Boot mode mismatch	For example, if the target instance type is a security-enhanced one that only supports the UEFI boot mode, the source instance must also support the UEFI boot mode.	Select a target instance type with a compatible boot mode.