As the hosting operator, plan recovery for your customer’s database before a PD AWS PostgreSQL service needs it. Manual snapshots and provider automated recovery are useful only when the correct recovery point is available and the restored database is connected to the application and billing service deliberately.

Establish the recovery point

Identify the original service, AWS backing, region and database. Record the required point in time and confirm that a usable manual snapshot or automated recovery point exists. RDS provisioning requests seven-day automated retention; Lightsail’s automatic recovery is separate from the manual snapshots listed in the customer page.

Do not infer that a missing customer-list entry means no recovery point exists. Ask the AWS administrator to verify the actual provider backup state. Preserve the original database and any required snapshot while planning the recovery.

Use the administrator’s recovery workflow

The module’s customer actions do not expose Restore, point-in-time recovery or snapshot export. The administrator must use the appropriate AWS workflow. RDS snapshot restoration creates a new DB instance; it does not overwrite the original in place. Lightsail can also create a new database from a recovery point.

A restored AWS resource is not automatically adopted by the original billing service. Record the source and destination separately and establish how the recovered database will be managed before changing module settings or retiring the source. Do not press Create again as an attempt to attach a separately restored resource.

Verify before cutover

Confirm the destination’s readiness, network access and working credentials privately. Check the recovered application data, then plan the application connection change and interruption window. Only after the recovery is verified should the administrator decide what to retain or remove. Keep the original service and recovery-point references with the observed recovery result.

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