Specification families that can be changed between prepaid instances and pay-as-you-go instances

This article introduces the specification families that can be changed for prepaid instances and pay-as-you-go instances, and focuses on its impact and variable instance specifications.

Change specification table

Impact

After changing the configuration, the following impacts will be had on different types of instances:

Classic network type instances:

For instance specifications that have been discontinued, when a non-I/O optimized instance is converted to an I/O optimized instance, the instance private IP address, disk device name, and software authorization code will change. For Linux instances, ordinary cloud disks (cloud) will be identified as xvda or xvdb, and efficient cloud disks (cloud_efficiency) and SSD cloud disks (cloud_ssd) will be identified as vda or vdb.

For instance type families on sale, the private IP address of the instance will change.

VPC type instance:

For instance specifications that have been discontinued, when a non-I/O optimized instance is converted to an I/O optimized instance, the cloud server disk device name and software authorization code will be changed. Variety. The ordinary cloud disk (cloud) of the Linux instance will be recognized as xvda or xvdb, and the efficient cloud disk (cloud_efficiency) and SSD cloud disk (cloud_ssd) will be recognized as vda or vdb.

Variable instance specifications

Description

Different instance specifications provide different availability zone information. During the configuration change operation, it depends on whether the target specification (family) is available in the current availability zone.

In the following table, the variable target specification family applies to prepaid instances and pay-as-you-go instances.

The above is the detailed content of Specification families that can be changed between prepaid instances and pay-as-you-go instances. For more information, please follow other related articles on the PHP Chinese website!