As the hosting operator, help your customer identify a manual snapshot the application no longer needs before using the client-area Delete action. Removing a snapshot is separate from rebooting the cache, cancelling the billing service or changing automated-backup retention.

Identify the intended copy

Open the active service’s Snapshots section and confirm its cache and AWS region. Match the snapshot name to the copy you intend to remove. Verify that another suitable recovery point exists where the application needs one; do not choose a snapshot only by its position or date in the list.

Some installations can show the same old date for several snapshots. Your hosting team should compare the actual snapshot name and time in AWS if the displayed date does not match the expected recovery point. Keep any uncertain copy intact until it has been identified.

Customer steps: submit the deletion

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

The page offers Delete for manual copies. Automatic backups are managed by the provider’s retention policy; this control does not change that policy. A queued request or Done entry needs checking against the resulting provider state rather than repeated clicks on similarly named copies.

Check the actual snapshot state

An empty list does not prove every snapshot was deleted: the read can fail or the result can be incomplete. Compare the original selected snapshot name and deletion result with your AWS account. Preserve uncertain recovery points and do not select similarly named copies or repeat a request simply to refresh the list.

See the PD AWS ElastiCache WHMCS guide for related tasks, or explore PD AWS ElastiCache.