You can release a pay-as-you-go ApsaraDB for MongoDB instance to stop incurring charges.
ApsaraDB for MongoDB does not support pausing instances. To stop billing, you can release the instance. However, releasing an instance makes data unavailable. For more information, see Precautions. If you want to retain data but temporarily stop using the instance, we recommend that you downgrade the instance specifications to reduce costs.
Prerequisites
The instance uses the pay-as-you-go billing method.
The instance is in the Running state.
Precautions
Released instances remain in the Recycle Bin for 7 days before being permanently deleted. Data cannot be recovered after permanent deletion, so proceed with caution.
You cannot restore released standalone instances from the Recycle Bin.
You cannot restore released sharded cluster instances that use local disks from the Recycle Bin.
You cannot restore released TDE-enabled instances from the Recycle Bin.
To restore a disk-encrypted instance from the Recycle Bin, ensure that its associated KMS key is available. The instance cannot be restored if the key is unavailable.
Release an instance
Log in to the ApsaraDB for MongoDB console.
In the left-side navigation pane, click Replica Set Instances or Sharded Cluster Instances, depending on your instance type.
In the upper-left corner of the page, select the instance's resource group and region.
Find the target instance. In the Actions column, click More > Release.
NoteIf a message states that release protection is enabled, you must first disable it. For more information, see Enable or disable release protection for an instance.
In the Release Instance dialog box, click Confirm.
The instance state changes to Releasing.
References
To release a node from a sharded cluster instance, see Release a mongos or shard node.