As the hosting operator, help your customer identify a manual cluster snapshot that is no longer needed before using the client-area Delete action. Deleting a snapshot removes that recovery point; it is different from stopping the database or removing the database service.

Identify the intended copy

Open the active customer service’s Snapshots section. Match the snapshot name, database and creation time to the copy you intend to remove. Establish whether another usable recovery point meets the application’s needs before proceeding. Do not identify a backup only by its position in the list.

DocumentDB listings can include automated backups. The customer page offers Delete for manual snapshots; that control does not edit the automated-retention policy.

Customer steps: submit and check the request

1. Select Delete beside the intended manual snapshot.
2. Read the confirmation and confirm only that snapshot.
3. Follow the request under Activity.
4. Reopen Snapshots after AWS processes it and check the result.

A deletion request can wait while the provider is busy. A Done entry records the operation result, while the provider list may need time to reflect the change. Keep the original request rather than repeatedly deleting similarly named copies.

Check the actual snapshot state

An empty list does not establish that every recovery point was removed: the read can fail and the displayed results are not a complete backup inventory. Compare the original selected snapshot and Activity result with your AWS account. Do not select similarly named copies as a way to refresh the list or repeat the request while its outcome remains uncertain.

If the wrong copy was selected, preserve the remaining copies and have your AWS/database administrator assess the available recovery options.

See the PD AWS DocumentDB Blesta guide for related tasks, or explore PD AWS DocumentDB.