Your hosting team should plan recovery before a customer’s PD AWS MariaDB service needs it. The administrator needs a usable RDS recovery point, a verified destination and a deliberate application cutover; the customer snapshot page is not an in-place Restore control.

Establish the recovery point

Identify the original service, AWS region and database. Record the required point in time and confirm that a usable manual snapshot or automated recovery point exists. Normal RDS provisioning requests seven-day automated retention. Verify the actual retained backup state before relying on that window for an existing database.

Do not infer that a missing customer-list item means there is no backup. Ask the AWS administrator to check the provider’s recovery points. Preserve the original database and any required snapshots while planning the recovery.

Use the administrator’s RDS workflow

RDS restoration from a snapshot creates a new DB instance; it does not overwrite the original database in place. The module’s customer dispatch does not expose Restore or point-in-time recovery. The administrator must use the appropriate AWS workflow and verify the resulting instance.

AWS can export supported MariaDB snapshot data to S3, but that analytics export is not a directly restorable RDS snapshot. The module does not provide a customer export action. Keep the required recovery point independently of any exported data.

Coordinate the destination and cutover

A separately restored AWS resource is not automatically attached to the original billing service. Your hosting team should record the original service, source database, recovery point and restored database separately. Verify the destination’s network access, working credentials and recovered application data before planning the application’s connection change. Preserve the source and required recovery points until your recovery checks and cutover plan are complete.

Do not treat editing an offering default or pressing Create as a way to attach the separately restored database to that service. This guide does not provide a reassociation procedure. Establish the supported management path for the restored resource before changing the original service’s configuration or retiring its database.

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