As the hosting operator, help your customer identify an unneeded manual snapshot and the recovery points that must remain before the client-area Delete action is used. Deleting a snapshot is a deliberate permanent change, separate from stopping the database.

Check the selected recovery point

Open Snapshots for the intended service. Compare the snapshot reference, creation time and status with the one you intend to remove. Confirm another verified recovery point or independent copy exists where it is required.

Do not treat an empty or incomplete list as proof that no backups exist at AWS. Automated backup retention is managed separately; the customer delete control is not a way to remove automated history.

Customer steps: delete and verify

1. Select the delete control for the intended manual snapshot.
2. Read the confirmation carefully and submit once.
3. Follow the request under Activity.
4. Refresh the snapshot list and verify the intended result.
5. Check that required remaining recovery points still exist.

A queued deletion is not proof that the provider already removed it. If the request fails or times out, inspect the original result before another attempt. Do not select a similarly named snapshot as a substitute.

Keep recovery and service removal separate

Deleting the database service can remove its matching module-owned snapshots too; keeping one here does not make service termination safe for that recovery point. Review service removal before ending the service.

Preserve remaining recovery points and involve your database administrator if the wrong copy was selected.

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