This topic describes the instance types and instance families that support instance type changes. If your current instance type does not meet your business needs, check whether the instance type can be changed. If yes, choose a method to change the instance type.
Impact of instance type changes
- Classic network-type instances:
- For instances of retired instance types, when the configurations of non-I/O optimized
instances are upgraded to those of I/O optimized instances, instance information including
the private IP addresses, disk device names, and software license codes is changed.
For Linux instances, the device names of basic disks (
cloud
) are identified as xvd* such asxvda
orxvdb
, and the device names of ultra disks (cloud_efficiency
) and standard SSDs (cloud_ssd
) are identified as vd* such asvda
orvdb
. - For instances of instance types that belong to an available instance family, the private IP addresses of instances are changed.
- For instances of retired instance types, when the configurations of non-I/O optimized
instances are upgraded to those of I/O optimized instances, instance information including
the private IP addresses, disk device names, and software license codes is changed.
For Linux instances, the device names of basic disks (
- VPC-type instances:
For instances of retired instance types, when the configurations of non-I/O optimized instances are upgraded to those of I/O optimized instances, instance information including the disk device names and software license codes is changed. For Linux instances, the device names of basic disks (
cloud
) are identified as xvd* such asxvda
orxvdb
, and the device names of ultra disks (cloud_efficiency
) and standard SSDs (cloud_ssd
) are identified as vd* such asvda
orvdb
.
Instance families that do not support instance type changes
- Big data instance families: d2c, d2s, d1, and d1ne
- Instance families with local SSDs: i1, i2, i2g, i2ne, i2gne, and i3
- GPU-accelerated compute optimized instance families: vgn5i and gn5
- FPGA-accelerated compute optimized instance families: f1 and f3
- ECS Bare Metal Instance families:
- ebmgn6e, ebmgn6v, and ebmgn6i
- ebmg6, ebmg5s, ebmg5, ebmc6, ebmc5s, ebmc4, ebmre6p, ebmr6, and ebmr5s
- ebmhfg6, ebmhfg5, ebmhfc6, and ebmhfr6
- Super Computing Cluster (SCC) instance families: scchfg6, scchfc6, scchfr6, sccg5, scch5, and sccgn6
Instance families that support instance type changes
Original instance family | Compatible instance family |
---|---|
t6 |
|
t5 |
|
s6 |
|
n4, mn4, xn4, and e4 |
|
Original instance family | Compatible instance family and type |
---|---|
g6, c6, and r6 |
Note
|
g6se |
|
g6a, c6a, and r6a | g6a, c6a, and r6a |
g6t and c6t | g6t and c6t |
g6e, c6e, and r6e |
Note To upgrade an instance type that belongs to the g6e, c6e, or r6e instance family to
an instance type that belongs to a seventh-generation instance family (hfc7, hfg7,
or hfr7),submit a ticket. You cannot downgrade the instance type of the instance after the upgrade is complete.
|
ebmg6a, ebmc6a, and ebmr6a | ebmg6a, ebmc6a, and ebmr6a |
ebmg6e, ebmc6e, and ebmr6e |
|
g5, g5ne, r5, c5, and ic5 |
Note
|
sn1ne, sn2ne, and se1ne |
|
se1 |
|
re6p | re6p |
re6 |
Note You can change the instance types of instances between ecs.ebmre6-6t.52xlarge, ecs.re6.26xlarge,
ecs.re4.40xlarge, and ecs.re4e.40xlarge.
|
re4 |
Note You can change the instance types of instances between ecs.ebmre6-6t.52xlarge, ecs.re6.26xlarge,
ecs.re4.40xlarge, and ecs.re4e.40xlarge.
|
hfc7, hfg7, and hfr7 | hfc7, hfg7, and hfr7 |
hfc6, hfg6, and hfr6 |
Note
|
hfc5 and hfg5 |
|
vgn6i | vgn6i |
gn6i | gn6i |
gn5i | gn5i |
gn6e | gn6e |
gn6v | gn6v |
t1, s1, s2, s3, m1, m2, c1, and c2 |
|
n1, n2, and e3 |
|
sn1 and sn2 |
|
c4, ce4, and cm4 |
|