Remove a PD AWS MySQL database service from Blesta
As the hosting operator, verify your customer’s recovery requirements before terminating a database service. PD AWS MySQL removal deletes the service’s provider resource and requires a deliberate recovery and cutover decision.
Verify a recovery copy before removal
Identify the intended service, account, region, backing and application dependencies. Establish the required recovery data and test a suitable independent copy with the AWS administrator before proceeding.
The module does not automatically take a final snapshot on termination. It can remove automated backup history and matching module-owned manual snapshots during cleanup. A manual snapshot shown on the module page is therefore not an independent copy protected from service removal.
Stopping a database is a different task. Use temporary power controls when the intent is a temporary interruption rather than deleting the service’s resource.
Submit the intended service removal
After the recovery and billing decisions are settled, use the original Blesta service’s cancellation workflow with Use module enabled when provider removal is intended. Read the confirmation and submit once for the intended service. Inspect PD AWS MySQL → Activity and Clients & Databases for the original result.
The provider can remove resources in the background. A successful billing response does not prove that the database and its related cleanup are already complete or that provider charges stopped. Have the responsible administrator confirm the actual result.
Handle a pending or mistaken removal
Do not use another Create or Uncancel request while the previous database is still being removed. Reactivating a billing record after teardown does not restore deleted data; recovery requires a usable retained or independent recovery point and a coordinated destination.
If removal was unintended, preserve any remaining recovery copies and involve your AWS/database administrator in assessing recovery.
Do not repeat removal against a similarly named database.
See the PD AWS MySQL Blesta guide for related tasks, or explore PD AWS MySQL.