An Active WHMCS service is a billing record, not proof that a Lightsail instance exists. First establish whether WHMCS called PD AWS Lightsail, whether the request is still pending, or whether it failed with a provider error.

Check the product setup choice

1. Open System Settings → Products/Services and edit the product attached to the service.
2. Under Module Settings, confirm PD Lightsail and the intended AWS server or server group.
3. Review Automatically setup the product. If the offering should provision after payment, select When the first payment is received rather than leaving setup manual.
4. Check the affected service’s invoice/payment state and module result. Saving a new automatic-setup choice does not prove that an older service has now been created.

Do not assume a product created with a generator has the setup choice you intend. Review the saved value on each offering. The product creation guide covers the full configuration.

Look for an in-progress or failed operation

Open PD Modules → PD AWS Lightsail → Clients & Services and Activity. Check the affected service and the time of the expected creation. If an instance is starting or networking is still being attached, allow that operation to finish rather than issuing a second create request.

If there is an error, record it and check the selected account under System Settings → Servers with Test Connection. A successful connection check does not establish every provisioning permission. Review the selected region, plan, blueprint and the permission named by the failing operation.

Compare the service with your AWS account

You operate the WHMCS installation and AWS account. Your customer’s service in WHMCS and the instance in Lightsail need to agree; an Active billing status alone cannot confirm that.

Using your own AWS access, check the Lightsail region selected for this product. Compare any instance details shown by the module with the resources in that region and the expected creation time.

• The instance exists and is still starting: let that operation finish, then check its state again. A second Create request does not resolve a pending operation.
• The instance exists, but WHMCS shows a failure or no connection details: record the discrepancy and the module error. Include these observations in a problem report rather than creating another instance for the same service.
• No instance exists and creation failed: use the actual error to identify the failed requirement, such as the selected region, plan, blueprint or AWS permission. Correct the identified setting before considering a manual Create action on the existing service.
• You cannot establish what happened: collect the module result and what you can see in your AWS account. Report that uncertainty explicitly; it is useful diagnostic information.

After creation succeeds, confirm that the intended instance is Running and that the connection details shown for your customer’s service agree with it. If the product includes an application, check that application separately.

See the PD AWS Lightsail WHMCS guide for related tasks, or explore the module.

Clients who need help with an unexplained module result can follow our reporting guide (client sign-in required).