Create a WHMCS product that defines the Lightsail instance your customer receives: its operating system, region, plan and available management controls. Configure the AWS connection first so the product can load the provider’s plans and images.

This guide covers a product with fixed defaults. Customer-selectable region, plan and operating-system options can be added afterwards.

Before you start

Install PD Modules and PD AWS Lightsail, connect your licence account and configure a working PD Lightsail server record in System Settings → Servers. Confirm its connection test succeeds. Decide which AWS account and region this offering should use.

Creating the product configures an offering. Activating or provisioning a service creates AWS resources and can incur provider charges.

Choose what this product includes

Start with the service you want to sell, then choose the settings that deliver it:

• Platform sets the operating-system family. Choose it before reviewing the available plans and images.
• Region sets where the new instance will be created. Use the location intended for this offering; a customer-selectable region can override the fixed default.
• Availability Zone chooses a zone within the selected region. Leave it on Auto when you want the default placement, or choose a specific zone when your offering needs one. It does not change the region.
• Instance plan (bundle) sets the server capacity. Compare RAM, vCPU, storage and transfer with the workload you intend to host.
• Blueprint (OS) sets the operating system or application image. Choosing more capacity does not choose or install a different application image.
• IPv6-only networking determines whether the offering uses an IPv6-only plan. Leave it off when you intend to offer a public IPv4 address.
• Allocate static IP requests a static public IPv4 address for a newly created service. Use it when customers need an address that stays the same across stop/start, and keep IPv6-only networking off for that offering.
• Client: Connection details, Client: Firewall and Client: Snapshots control the corresponding customer tools. Enable the tools included in your service, rather than assuming every customer should receive every control.

Give the offering a useful resource label

Tag name supplies the AWS resource’s Name tag for resources created from this offering. For example, a fixed label such as managed-web can help your team recognise resources belonging to that offering. It is a label, not the customer’s domain or a unique name for every server.

Leave it blank to use the module’s generated instance name as the display tag. Saving a different label is not a bulk rename of existing customer resources.

Example: a Linux server offering with a fixed location

Suppose you want customers to order a Linux server in one location, with a static IPv4 address and direct SSH access. This is an example configuration, not a requirement for every hosting business.

Choose the Linux/Unix platform, your intended region, an available Linux blueprint and a plan with suitable capacity. Leave IPv6-only networking off, enable Allocate static IP, and enable Client: Connection details so customers can obtain the service's SSH details. Decide separately whether your service includes customer-managed firewall rules and snapshots.

Keep the region, plan and OS fixed while you check this initial offering. If you later expose those dimensions at checkout, review the available combinations and prices before accepting orders. Use the current lists in your installation instead of copying an old plan or image identifier from an example.

Create the product

1. Open System Settings → Products/Services → Create a New Product.
2. Choose the product group and enter a name customers will understand.
3. Set the product type to Other Products/Services. Use this type for PD Lightsail, even though the resource being sold is a cloud server.
4. Open Module Settings and select PD Lightsail as the module. Select the intended server or server group for the AWS connection.
5. Set Platform for the operating-system family you are offering, then select Region and Availability Zone as appropriate.
6. Choose Instance plan (bundle) and Blueprint (OS). The plan defines capacity; the blueprint defines the operating system or application image. Review both rather than treating the names as interchangeable.
7. Review networking, static IP and backup settings. Choose which client controls the product exposes, including Client: Connection details if customers should obtain SSH access information from their service page.
8. Set Automatically setup the product to the behaviour you intend. For provisioning after a customer’s first payment, choose When the first payment is received. Do not leave setup manual if the offering promises automatic provisioning.
9. Set the customer’s billing terms and prices on the product’s Pricing tab. Choose the intended welcome email under Other, then save.

Check before accepting orders

Reopen the saved product and confirm the module, AWS connection, region, bundle and blueprint. Check that the enabled client controls match the service you intend to provide.

Review the automatic-setup selection explicitly. An order or service status alone is not proof that an AWS instance was created. Provisioning must complete and the provider resource must be present before the customer can manage a running server.

Use your controlled first-service test process when ready to provision. Confirm the instance reaches its expected running state and that the customer’s connection details correspond to that service.

If plans or images do not load

Return to the selected WHMCS server record and run Test Connection. Check the saved AWS credentials, permissions and selected region before changing the product’s defaults.

If a paid service has no instance, inspect the product’s automatic-setup choice and the service’s module result. Resolve the reason before repeating Create, so a slow or partially completed request does not lead to duplicate resources.

The WHMCS Lightsail overview introduces the complete offering. Explore PD AWS Lightsail for WHMCS for module details.

Configure the next part of your offering

• Choose customer controls
• Manage customer SSH public keys
• Allocate a static IP on an existing server
• Configure a startup script for new servers