Docs

Elastic Compute Service

Elastic Scheduled Instance

Delete Elastic Scheduled Instances (ESI)

Elastic Scheduled Instances (ESI) are not automatically released. After your business operations are complete, you can refer to this document to delete Elastic Scheduled Instances (ESI) in the console.

warning

Elastic Scheduled Instances (ESI) with a usage duration of less than one hour will be billed for a minimum billing period of one hour. Please refer to the bill for the actual charges. What is the 1-hour minimum consumption?

After Elastic Scheduled Instances (ESI) and their associated resources are deleted, billing stops immediately. Why is the instance still being billed after it has been deleted?

Methods of operation

tip

During the deletion process, do not perform any actions on resources attached to the instance; otherwise, this may cause ECS failures or resource deletion failures.

Delete an instance on the reservation order list page

Delete an instance on the Instances page

Precautions

Only ESI orders with status Delivered or Partially Delivered Failed support batch deletion of all unreleased instances in the order.

If you delete an instance on the ESI order list page, the status of resources related to the instance after deletion is shown in the following table.

Resource	Situation after deleting an instance
System Volume/Local Volume	Released automatically with the instance. After release, data will be automatically cleared and cannot be recovered. Please make sure to perform data backup in advance.
Data Volume	It depends on whether the option to delete the Data Volume with the instance is selected when creating the instance or mounting the Volume: If you delete an instance, the Data Volume will be released together with the instance and cannot be recovered. Please make sure to back up your data in advance. If not, when you delete the instance, the Data Volume is disassociated from the instance, is not released automatically, the data on the volume is retained by default, and billing continues. You can still mount the Data Volume to other instances.
Elastic IP address (EIP)	The EIP associated with the primary private IP address of the instance's primary network interface depends on whether the Delete with instance option is selected when you create an instance or associate an EIP with an instance: If so, when you delete the instance, the EIP is released along with the instance. If not, when you delete the instance, the EIP will be automatically disassociated from the instance, will not be automatically released, and will continue to be billed. You can still associate the EIP with other instances. EIPs associated with the secondary private IP address of the primary network interface, as well as EIPs associated with the secondary network interface, are disassociated from the instance, are not automatically released, and billing continues. You can still associate the EIP with other instances.

Procedure

In the top menu bar, select the region and project where your business is located.

Access the batch delete instance page using any of the following methods.

On the reservation order list page, click the "Batch delete" button in the actions column for the target reservation order.

On the reservation order list page, click the name of the target reservation order to enter the details page. Then, click the "Batch delete" button in the upper right corner.

In the pop-up dialog box for batch deleting instances, confirm the instance information.

Select the checkbox for "I am aware of the Instances and related resources that are about to be deleted and understand the associated risks." then click the "Delete" button to complete the deletion operation.

Results of actions

After performing the delete operation, the instance status changes to deleting. After a short time, the instance is deleted and removed from the list.