Define the database a customer should receive through PD AWS SQL Server. Connect AWS first, then configure a new product before offering it for sale. SQL Server uses Amazon RDS; Lightsail managed databases are not a SQL Server alternative in this module.

Set the offering defaults

1. Open System Settings → Products/Services → Products/Services and create a product in the intended group.
2. Choose the Other product type.
3. On Module Settings, select PD AWS SQL Server and the intended server group.
4. Set Backing service to Amazon RDS and review region, plan, SQL Server version, storage and public access.
5. Review the customer controls and set the intended pricing.
6. Set Automatically setup the product explicitly if automatic provisioning is wanted, such as when the first payment is received, then save.

This module provisions SQL Server Standard Edition on RDS. It creates an instance, not a named application database; customers create their application databases after connecting. Choose the intended region and a suitable SQL Server instance class together. Check the engine version and storage available for that combination, rather than treating a saved example as current AWS availability.

Review customer choices

Open PD Modules → PD AWS SQL Server → Products and locate the saved product. Generate options creates the module’s configurable-option group. Review choices and prices under System Settings → Products/Services → Configurable Options; the product’s own Configurable Options tab assigns groups.

Read confirmations before rebuilding. Rebuild from AWS resets generated prices to defaults. Visibility changes preserve prices, but this does not establish that a hidden selection on an existing order will be discarded. Review the actual accepted service values as well as the form’s visible choices.

Check the first service

A paid or Active billing record is not proof that a working database exists. Inspect Clients & Databases and Activity, then compare the original request with the resource and region visible in your AWS account. Wait for the provider’s availability result. Your hosting team should verify the displayed connection details with the intended application before accepting the service as ready. If details are missing or the module and AWS disagree, record that discrepancy before requesting another creation.

Use your normal controlled first-service test after checking AWS charges and network access. Keep the original service record while investigating a failure.

See the PD AWS SQL Server WHMCS guide for related tasks, or explore PD AWS SQL Server.