Release a pay-as-you-go ApsaraDB for MongoDB instance that you no longer need. Released instances are held in the Recycle Bin for seven days before permanent deletion. After permanent deletion, instance data cannot be restored. Exercise caution when you release an instance.
The following instance types cannot be recovered from the Recycle Bin after release: standalone instances, sharded cluster instances that use local disks, and instances with Transparent Data Encryption (TDE) enabled. For these instance types, release is permanent. Back up your data before proceeding.
Prerequisites
Before you begin, make sure that:
The billing method of the instance is pay-as-you-go
The instance is in the Running state
Release an instance
Log on to the ApsaraDB for MongoDB console.
In the left-side navigation pane, click Replica Set Instances or Sharded Cluster Instances.
In the upper-left corner of the page, select the resource group and region where the instance is located.
If release protection is enabled for the instance, disable it first. When release protection is active, the following prompt appears: *"The operation cannot be performed because release protection is enabled for the instance. To release the instance, disable release protection for the instance first."* To disable it, see Enable or disable the release protection feature for an instance.
Find the instance and click More in the Actions column. Then select Release from the drop-down list.
In the Release Instance dialog, click OK.
The instance enters the Releasing state. After release completes, the instance moves to the Recycle Bin (if eligible) and is permanently deleted after seven days.
To recover an instance that has disk encryption enabled from the Recycle Bin, the Key Management Service (KMS) key must be available. If the key is unavailable, the recovery fails.
What's next
To release a mongos or shard node from a sharded cluster instance, see Release a mongos or shard node.