If the current instance configurations of an instance cannot meet your business needs, you can change its instance type (vCPUs and memory), bandwidth configurations, and the billing method of its data disks. This topic describes methods to change the configurations of an ECS instance.
Change instance types
The vCPUs and memory size of instance types are predefined. To change the instance type of an instance, you must change the number of vCPUs and memory size together. You cannot modify only vCPUs or memory size.
The following table describes the change methods best suited for different billing methods applied to your instances.
|Billing method||Change time||Effective time||Operation|
|Subscription||Before the instance expires||After you restart the instance|
|Within 15 days before the instance expires||After you restart the instance and within the first seven days of the new subscription duration||Downgrade instance configurations during renewal|
|Pay-as-you-go||N/A||After you restart the instance||Change the instance type of a pay-as-you-go instance|
Change the billing method for network usage
You can use different methods to change the billing method for network usage based on the public IP address type. The following table lists the methods.
|Public IP address type||Effective time||Operation|
|Assigned public IP address||Immediately||Change the billing method for network usage|
|Elastic IP address (EIP)||Immediately||Modify the bandwidth of an EIP|
Modify public bandwidth
The methods you can use to modify the public bandwidth of an instance depend on your business needs and the billing method of the instance. The following table lists the methods.
- For a VPC-type ECS instance, its public IP address is released immediately.
- For a classic network-type instance, it cannot access the Internet but its public IP address is retained.
You can set the public bandwidth to a non-zero value when you create an instance. The system will allocate a public IP address to your instance. If you do not assign a public IP address when you create an instance, the instance has no public bandwidth. You can change the public bandwidth from 0 Mbit/s to a non-zero value by using the configuration upgrade feature to assign a public IP address to the instance.
|Public IP address type||Application scope||Effective time||Reference|
|Assigned public IP address||Modify the basic public bandwidth for a subscription instance||Immediately||Modify the bandwidth configurations of subscription instances|
|Modify the basic public bandwidth for a subscription instance during renewal||After the new subscription duration starts||Downgrade instance configurations during renewal|
|Modify the basic public bandwidth of a pay-as-you-go instance||Immediately||Modify the bandwidth configurations of pay-as-you-go instances|
|EIP||Modify the bandwidth of an EIP for a subscription or pay-as-you-go instance||Immediately||Modify the bandwidth of an EIP|
Change the billing methods of data disks
Only pay-as-you-go data disks can be attached to pay-as-you-go instances. Therefore, you can only change the billing methods of data disks for subscription instances.
|Operate time||Effective time||Operation|
|Before the instance expires||Immediately||Change billing methods of disks|
|Within the 15 days before the instance expires or after the instance expires but before it is released||Immediately||Downgrade instance configurations during renewal|
The following section provides answers to the FAQ about upgrading and downgrading the configurations of instances. For more information, see Instance FAQ.
- How is the cost of an instance upgrade calculated?
When you upgrade the instance type and configurations of an instance, the cost and its calculation method are displayed in the ECS console. You can also view the billing details on the Account Overview page.
- Will my cloud service configurations be affected when I upgrade ECS instances?
Pay-as-you-go instances must be stopped before they can be upgraded. After you upgrade the instance type of a subscription instance, you must restart the instance for the new configurations to take effect. The upgrade operation will interrupt services running on the instance for a short period of time. We recommend that you upgrade instances during off-peak hours. Instances can seamlessly resume services after upgrades without having to reconfigure their environment.