As the hosting operator, explain snapshot deletion to your customer and establish that the intended manual copy is no longer needed before the client-area Delete action is used. 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.

RDS 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.

If the result is unclear

An empty list does not prove that every copy was deleted. As the hosting operator, compare the selected snapshot reference, region and recorded result with the snapshots visible in your own AWS account. Distinguish a failed request, a deletion still being processed and a read/listing problem. Leave unrelated recovery points intact while checking that result.

If the wrong recovery point was selected, preserve the remaining snapshots and work with your database administrator on the available recovery options.

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