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 System Settings → Products/Services → Products/Services and create a product in the intended group.
2. Select the Other product type.
3. On Module Settings, select PD AWS MySQL and its intended server group.
4. Choose the region, Backing service, Plan, MySQL version, storage and public-access defaults.
5. Review the customer feature controls.
6. Set Automatically setup the product to the intended policy, such as setup when the first payment is received, then save.

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

Confirm that provisioning ran

An Active WHMCS billing record is not proof that module provisioning ran. Check the automatic setup policy and original payment event, then inspect Clients & Databases and Activity.

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 WHMCS guide for related tasks, or explore PD AWS MySQL.