Your hosting team should plan MySQL recovery around a usable recovery point, a verified destination and application checks. PD AWS MySQL provides snapshot controls, but its customer page does not expose a snapshot or point-in-time Restore action.

Establish the recovery point first

Identify the original service, AWS account, region, backing and required recovery time. Have your AWS administrator confirm the actual available manual snapshot or automated recovery window. The module list is not an exhaustive inventory, especially for automated Lightsail history.

Keep the original service and any required independent backup until recovery is verified. Do not terminate the service to start a restore: termination can delete its database, automated backups and matching module-owned manual snapshots without creating a final snapshot.

Coordinate the provider restore

The AWS administrator performs the appropriate RDS or Lightsail recovery workflow. A restore creates a separate database; it does not automatically attach that resource to the existing billing service. Establish how the recovered database will be tracked and managed before changing the original service.

For Lightsail, AWS documents creating a database from a snapshot. Do not assume a new provider resource will inherit the original endpoint, login or all network settings.

Verify the recovered application

Confirm the recovery time, required data, current connection details, TLS and allowed network path. Test the application’s actual recovery requirements before cutting it over or retiring the original.

A billing reactivation or a new order does not recover deleted data. Your hosting team should record the original service, source database, recovery point and separately restored destination. Verify the application and its connection to that destination before retiring the source. Do not assume that a normal module Create action attaches an arbitrary restored database to the original service; establish the supported management path before changing that service.

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