Choose the backing service before offering a MySQL database through PD AWS MySQL. Amazon RDS and Lightsail use different plans and expose different management capabilities in the module.

Match the backing to the intended service

Amazon RDS supports in-place instance-class changes, storage growth, supported high-availability choices and the module’s per-database IP firewall. Lightsail uses its database bundles; the module does not offer in-place resizing, separate storage growth or that IP firewall for Lightsail databases.

Both backings provide connection details, supported power controls, manual snapshots and performance metrics. Customer controls also depend on the host-enabled package settings. A capability at AWS is not automatically a button in the module; recovery operations need a separate administrator workflow.

Save the backing and matching choices

1. Open the package’s Module tab.
2. Choose Backing service and the intended region.
3. Select a matching Plan and review the engine-version choice.
4. Review RDS storage and any supported public-access choices.
5. Save, then generate or review the matching checkout options.
6. Check the actual accepted order before provisioning.

Use option generation to review values, visibility and prices. Do not infer that a curated fallback plan is available for every account or region.

Treat a backing change as a migration

Changing the package’s backing does not move an existing database. AWS can create a larger Lightsail database from a snapshot, but that is a new resource, rather than this module’s in-place resize. Establish data recovery, tracking and application cutover with the AWS administrator before retiring the original.

See RDS plan changes or recovery planning for those separate tasks.

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