As the hosting operator, you can let your customers create a recovery point from their PD AWS Lightsail service’s Snapshots page. This guide covers the access you enable, the customer steps and the checks your hosting team can make if a request does not complete.

Before you take a snapshot

Check Client: Snapshots in the product’s Module Settings and the controls available on the affected service. Confirm that the service has room in its manual-snapshot allowance. Your customer then opens the correct Lightsail service in the WHMCS client area and checks the server name, region and current state.

For a database or application that is actively writing data, use its normal backup or consistency procedure before taking the infrastructure snapshot. A successful snapshot request alone does not prove the application can recover to the state you need.

Customer steps: create the recovery point

1. Open Snapshots on the service-management page.
2. Review the existing snapshots so you do not confuse an older recovery point with the new one.
3. Choose Take snapshot and review the confirmation. The module supplies the snapshot name.
4. Confirm once, then watch its status and the service’s Activity.
5. Wait until the snapshot is available before relying on it for recovery. A pending or requested operation is not a completed snapshot.
6. Record the snapshot name, creation time and the application change it precedes in your own maintenance notes.

Snapshot storage can incur provider charges. If the service has reached its manual-snapshot allowance, review which older recovery points are still needed before deleting anything. Do not remove the only useful backup simply to make room for a new attempt.

Understand what appears in the list

The module lists the service’s manual snapshots, including eligible recovery points from before a restore or plan change. AWS-managed daily automatic snapshots are separate and do not appear in this customer list.

The module’s restore workflow moves the current extra storage disk to the replacement server unchanged. Do not assume that choosing an older server snapshot will roll back that disk’s current data. Read the restore guide before using a recovery point.

Remove an older manual snapshot

Review the recovery points with your customer and identify one that is no longer needed. Check its name and creation time before deleting it; deletion removes that recovery point.

1. Open Snapshots for the correct service.
2. Find the intended manual snapshot and choose Delete on its row.
3. Check the snapshot name in the confirmation, then confirm only if it is the recovery point you intend to remove.
4. Wait for the operation to finish. Refresh the snapshot list and check that the selected snapshot has disappeared and the used allowance has decreased.

If the list has not changed yet, check Activity before submitting the operation again. Once there is a free slot, Take snapshot becomes available for a new recovery point. An allowance of zero means that manual snapshots are not included; deleting an old snapshot does not change the service’s allowance.

If the request fails

Open the affected service under PD Modules → PD AWS Lightsail → Clients & Services and read Activity. Check whether the request is still in progress, failed or completed. If the allowance is full, review the recovery points your customer still needs before deciding how to make space. For a displayed AWS permission or capacity error, check the requirement identified by that error in your own account.

If the result is uncertain, compare the service’s snapshot list with the snapshots visible in the selected AWS region. Record whether the requested recovery point exists and its current state before submitting another request.

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