Offer customer-selectable MySQL plans and other supported dimensions through PD AWS MySQL. The generated choices must match the package’s saved region and backing service.

Generate and price the choices

1. Save the intended backing, region and defaults on Module.
2. Open PD Modules → PD AWS MySQL → Products and locate the package.
3. Choose its generate-options action and read the confirmation.
4. Review the resulting choices and prices under Packages → Options.
5. Check which dimensions are visible on the actual order form.
6. Compare an accepted selection with the resulting service.

The module initially exposes Plan and can generate additional supported choices such as Region, Version and public access, with RDS-only storage or high availability where applicable. A generated choice is not proof that every class/version combination remains available at AWS.

Distinguish rebuild from visibility changes

Generating again can rebuild existing options and reset their generated prices. Record your values and prices before confirming a rebuild, then review them afterwards. Do not rebuild merely to change which existing dimensions are visible.

The visibility controls and Sync with AWS, where offered, serve different tasks. Sync can update retired/new choices without repricing existing ones; inspect its proposed scope and result. The accepted choices of existing customers still require deliberate review rather than an assumed migration.

Keep hidden choices and defaults consistent

A generated dimension kept off checkout uses the package’s matching module default. Verify default storage, version, plan, region and public access before hiding a choice. Changing an existing database’s engine version is not performed merely by editing a generated Version option.

See region selection and RDS plan changes before applying configuration changes to existing services.

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