Create an AWS Lightsail package in Blesta with PD AWS Lightsail
A Blesta package defines the Lightsail instance customers order: the provider account, operating system, region, plan and service controls. Add a working AWS account in the module before creating the package.
This guide starts with fixed package defaults. Customer-selectable options can be introduced after the basic offering is configured.
Before you start
Install PD Modules and PD AWS Lightsail, connect the licence account, and add the AWS account through Settings → Company → Modules → PD AWS Lightsail → Manage. Confirm the account’s connection test succeeds.
Decide which account, operating-system family and region this package should use. Creating the package prepares the offering; activating a service creates AWS resources and can incur provider charges.
Choose what this package 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 package
- Open Packages → Packages → Add Package.
- Select PD AWS Lightsail as the module and choose the intended AWS account.
- Give the package a clear name and choose its package group.
- Review the module settings. Set Platform, Region and Availability Zone for this offering.
- Choose Instance plan (bundle) and Blueprint (OS). Select a plan matching the intended platform and networking choice, and an image matching the operating system or application you want to deliver.
- Review static IP, networking and automatic-snapshot options rather than accepting them without checking what the package includes.
- Choose the allowed client controls. Enable Client: Connection details if customers should obtain their server’s SSH connection information from the service page.
- Set the package’s terms, customer prices and welcome email, then save.
- Add the package group to the intended order form under Packages → Order Forms when it is ready to sell.
The region, plan and image defaults describe the resource to create. They are separate from the package group and order form that make the offering available to customers.
Understand when provisioning occurs
Blesta provisions the provider resource when the service is activated. Its Provision Paid Pending Services task handles eligible paid pending services; packages configured to hold paid services for manual activation need a staff activation instead.
Review the package’s activation behaviour and the company’s normal automation. A service can remain pending while activation or provider setup is incomplete. Do not treat the presence of an order as confirmation of a running Lightsail instance.
Check the first service
Reopen the package and confirm its selected account, platform, region, bundle, image and client controls. When ready, use your controlled first-service test process.
Check that the activated service obtains its expected provider instance and reaches the correct state. Open the customer’s service view and confirm that the enabled controls and connection details belong to that service.
If configuration lists are empty, check the saved module account and its connection test. If activation fails, review the service result and package account before retrying; reconcile any partially completed provider work first.
Use the Blesta Lightsail overview for context, or explore PD AWS Lightsail for Blesta for module details.
