Define the database a customer should receive through PD AWS SQL Server. Connect AWS first, then configure a new package 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 Packages → Packages → Add Package.
2. Select PD AWS SQL Server and the intended module account.
3. On Module, set Backing service to Amazon RDS and review region, plan, SQL Server version, storage and public access.
4. Review the customer controls, package name, pricing and package group, then save.
5. Add the package group to the intended form under Packages → Order Forms.
6. Review Provision Paid Pending Services under Settings → Company → Automation, applicable client-group automation and the running cron. Staff activating a pending service must select Use module when a database should be provisioned.

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

Set the database dimensions on the package’s own Module settings. This module’s Products panel can direct you back to package settings instead of generating a checkout group. Do not follow instructions to press a generator button that is not offered on that installation. Keep the package’s actual defaults and customer-facing description consistent.

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 Blesta guide for related tasks, or explore PD AWS SQL Server.