Elastic Compute Service:Release an instance

Impacts and risks

• Data loss: When you release an instance, its local disks, system disk, and any data disks configured to be released with the instance are also released. It also deletes any automatic snapshots set for deletion with their associated cloud disks.

  Workaround: Back up your data. Manually create a snapshot or create a custom image in advance.

• IP address loss: The static public IP address of the instance is reclaimed and cannot be recovered.

  Workaround: Convert the static public IP address to an Elastic IP Address (EIP).

• Ongoing charges: Independent cloud resources, such as disks, EIPs, and snapshots that are not configured to be released with the instance, are not deleted and will continue to incur charges.

  Workaround: After releasing the instance, check your billing to identify and manually release any remaining billable resources.

Release a pay-as-you-go instance

Release a subscription instance

Instance release protection

When release protection is enabled, the system rejects all manual release requests initiated from the console, an API, or the CLI. This prevents instances from being accidentally released due to human error or malicious actions.

Apply in production

In a production environment, follow these best practices to ensure your resources are secure:

• Enforce release protection: Enable Release Protection for all production instances to prevent accidental deletion of core assets.

• Use access control: Grant permissions to release instances (ecs:DeleteInstance and ecs:DeleteInstances) only to authorized personnel. To enhance security, separate the permission to modify instance attributes (ecs:ModifyInstanceAttribute), which includes disabling Release Protection, from the permission to delete instances and assign them to different roles.

• Use ActionTrail: Enable ActionTrail to log all operations within your account. Configure alert rules for high-risk events, such as DeleteInstance and ModifyInstanceAttribute, to receive immediate notifications. This enables event tracking, auditing, and rapid response.

FAQ

• Why is the "Release" button for my instance grayed out?

  The instance may be an unexpired subscription instance. You must first switch its billing method to pay-as-you-go before you can release it.

• What is the difference between stopping and releasing an instance?

  These operations are fundamentally different.

  • Stop: This operation is like shutting down a computer. You can start the instance at any time to resume its operation.

  • Release: Releasing an instance permanently deletes it, along with its system disk, local disks, and any data disks configured for release. This data cannot be recovered. After an instance is released, it is removed from the instance list.

• Can I recover an instance that was accidentally released?

  No. Releasing an instance is a permanent and irreversible action. The system retains no data or configuration from a released instance, making recovery impossible. Always back up data before you release an instance.

• I released an instance, but why am I still being charged?

  Releasing an instance does not automatically release all of its associated resources. Check your billing to determine whether you are still being charged for associated resources that are billed independently, such as cloud disks, EIPs, or snapshots.

• How can I release multiple instances at once?

  • Console: Perform batch operations on the Instances page.

  • API: Call the DeleteInstances operation.

• How can I cancel a scheduled release?

  On the ECS console - Instances page, click the instance ID to go to its details page. In the Basic Information section, find Auto-release Time and click Cancel.