Define the MySQL database your customer receives through PD AWS MySQL. Connect AWS first, then choose a backing and plan that match the intended offering.

Configure the offering

1. Open Packages → Packages → Add Package.
2. Select PD AWS MySQL and the intended module account.
3. On Module, choose region, Backing service, Plan, MySQL version, storage and public-access defaults.
4. Review the customer feature controls.
5. Set the package name, pricing and group, then save.
6. Include that group in the intended form under Packages → Order Forms.

Use the RDS and Lightsail comparison before promising resizing or an IP firewall. A hidden checkout dimension uses its package default; a visible accepted selection can override it. Review the actual choices and defaults together.

Confirm that provisioning ran

Keep Provision Paid Pending Services enabled under Settings → Company → Automation, allow automatic paid-pending provisioning for the applicable client group, and keep cron running. Staff activating a pending service must select Use module. Payment alone is not proof that AWS provisioning completed.

AWS creates the real database in the background. Confirm its recorded backing and region, then inspect the current provider status and endpoint. A job request being accepted or a billing status changing does not establish a database is available for application connections.

Verify the customer result

Creating a database can incur provider charges. Review the account, plan and network access before using your normal controlled first-service test; repeated orders are not a way to investigate an uncertain operation.

Check the client Overview and intended feature pages once ready. Follow the TLS connection guide and test the application’s required operation. If setup remains pending or fails, use provisioning checks without deleting the original service as a reset.

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