PD AWS Lightsail for Blesta

PD Lightsail lets a hosting company sell Amazon Lightsail cloud servers as its own VPS product. Your customer orders in your Blesta order form, the server is built in your AWS account when Blesta activates the service, and your customer manages it from your client portal: a control panel that carries your brand and never mentions AWS. You set the price, AWS bills you the cost, and the difference is your margin.

It is built for hosts who want to offer cloud servers without building a control panel, without handing out AWS access, and without a support ticket every time a customer needs a reboot.

Why hosts choose PD Lightsail

Sell cloud servers under your own brand. Your customers see your company, your prices and your client portal. Amazon is never named on their pages, and they never need an AWS login.

Every order sets itself up. The server is created when Blesta activates the service, with the region, plan and operating system the customer picked on the order form. Suspend, unsuspend and cancel follow your normal Blesta billing, so a missed payment stops the server and a payment starts it again.

Customers help themselves. Power controls, connection details, snapshots, a firewall, static IPs, SSH keys, usage graphs and an optional in-browser terminal are all on the customer's own service page. That is most of the tickets a VPS product normally generates.

Packages that stay current. Plans and operating system images are read live from your AWS account. A daily check tells you when AWS retires something your order form still offers, and one click of Sync hides it from new orders without touching existing customers or your prices.

Pricing with the cost in view. Price Analysis shows the live AWS monthly cost of every Lightsail plan next to a suggested price at the margin you set, so you start from real numbers. It is a starting point to review: the figure leaves out extra storage, snapshots and static IPs.

Nothing left billing. Cancelling a service removes the server, its static IP, its extra disk, its snapshots and its key pair, then confirms at AWS that everything is really gone. No forgotten resources on your AWS bill.

How it works

1. Connect your AWS account. Add your AWS keys once as a module account under Settings, Company, Modules. Root keys work, and so does a least-privilege IAM user using the policy we ship. Test Connection checks every account you have added.
2. Create your packages. Pick a plan and an operating system, or let customers choose. One click generates the order options (region, plan, operating system, extra storage, static IP and automatic daily snapshots) from your live AWS catalogue, priced at your target margin for you to review.
3. Your customer orders. They choose their options on the order form and pay. When Blesta activates the service the server is built in your account and its own SSH key is generated; the customer's page shows progress until it is ready.
4. You get paid, they manage it. Blesta keeps billing as usual. When a customer upgrades to a larger plan, the server is moved up and keeps their data.

What you get in Blesta

Selling and pricing

• Order options generated from your live AWS offerings: region, plan, operating system, extra block storage, static IP and automatic daily snapshots
• Choose which options customers see; anything you hide is fixed to your package's setting, and changing what is shown keeps your prices
• Price Analysis with the live AWS cost of every plan, searchable and sortable, and a suggested price at your target margin
• IPv6-only plans for a cheaper package without a public IPv4 address
• Windows and Linux plans, each with the right connection details for the customer
• Package form fields that carry guidance, with plan and image lists read from your own AWS account
• More than one AWS account if you need them

Provisioning you can trust

• Orders that ask for a plan, image or region AWS no longer offers are refused before anything is created, with a clear reason
• A failed setup is never shown as done: the customer is told your team will help, and the failure is recorded for you in the module log and Activity
• Data-preserving upgrades: the server is moved to the larger plan with its data, firewall rules, static IP and automatic snapshots intact
• Downgrades and Linux-to-Windows switches are refused with a clear message instead of being attempted
• A startup script and tag name per package, applied to every server

Running it day to day

• Clients and Services: every server with its owner and live state, with Start, Stop, Reboot and a Retry for a stuck order
• Logs of every provisioning and AWS operation, searchable, plus task history across all services
• A products overview that shows what each package still needs before it can go live
• A ready-made welcome email that tells the customer how to reach and manage their server

What your customers get

• Start, stop and reboot, with buttons that only appear when they make sense
• Connection details ready to copy: the IP addresses, SSH user, a private-key download and the exact ssh command; on Windows, the RDP details instead
• An in-browser terminal to their server with no SSH client and no key handling (you switch it on per package)
• Snapshots they take, restore in a click and delete, up to the allowance they bought, plus Lightsail's own automatic daily backups (the latest seven kept)
• A firewall they manage themselves: open and close ports for TCP, UDP or ping without a support ticket
• A static IP they can add and release themselves
• Their own SSH keys, added on the SSH Keys page and applied on the next rebuild
• Reinstall with a fresh operating system, behind a typed confirmation
• Usage graphs for CPU and network in and out
• Recent activity in plain words: created, started, stopped, snapshotted, each with a time and a result

Every one of these is a switch on the package. Turn one off and it disappears from the customer's page, and the server refuses it too. The pages appear as tabs of the service in Blesta's client portal, follow its theme and are fully translatable, with wording overrides that survive updates.

Security built in

• AWS keys live only on the Blesta module account, stored encrypted, never on a customer page.
• Every server gets its own SSH key pair. Your AWS account's default key is never placed on a customer's server.
• Private keys are held encrypted on your own server, and only the signed-in owner of a service can download one.
• The in-browser terminal is off until you switch it on. Each session is checked against the service's owner, sealed, single-use and expires in about a minute. The key never reaches the browser in readable form, and nothing inbound ever reaches your Blesta server: no firewall rule to open, no endpoint to expose.

One product, every feature

PD Lightsail is one paid module with everything included: provisioning, power, snapshots, firewall, static IPs, metrics, upgrades and the browser console. There are no add-on tiers to compare. It installs into PD Modules in one click, updates itself, and uninstalls cleanly without modifying any Blesta files.

If your subscription ever lapses, your customers are not cut off. You get a 14-day grace period with everything working, then admin management locks while customers keep their servers, and only after that do customer features pause, behind a neutral "contact support" message that never mentions licensing. The servers themselves keep running in your AWS account throughout.

Requirements

• Blesta 6 or later on PHP 8.2 or later, with the ionCube Loader
• An AWS account with Lightsail access (root keys or an IAM user with the policy we provide)
• PD Modules, the free control panel every PD module installs into