PD AWS EC2 for Blesta

PD AWS EC2 lets a hosting company sell Amazon EC2 cloud servers as its own product. Your customer orders in your Blesta order form, the instance is launched in your AWS account with the instance type, region and operating system they picked, and they manage 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 EC2 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 AWS EC2

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

Every order sets itself up. The instance is launched when Blesta activates the service, exactly once, with its own firewall, its own SSH key and the options the customer chose on the order form. Suspend stops the server and keeps its disk, unsuspend starts it again, and renewals leave it running, so your normal Blesta billing drives the server.

A stable address from the start. Each server gets a stable public IP a few minutes after it is created and keeps it across stops and starts, so a customer can point DNS at it and leave it there.

Customers help themselves. Power controls, connection details, backups, a firewall, extra disks, 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 server product normally generates.

Packages that stay current. Instance types and images are read live from your AWS account. Images are tracked by family, so every order launches the latest patched image of the operating system chosen. 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.

Nothing left billing. Cancelling a service terminates the instance and its root disk, releases its stable IP and removes its firewall, key pair, extra disks and backups, then verifies the teardown. 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, using an IAM user with the policy we ship. Test Connection checks every account you have added and names AWS's own reason if something is wrong.
2. Create your packages. On the package form, Region, Instance type and Image are lists read from your own AWS account, not boxes to type identifiers into. One click generates the order options (region, instance type, operating system, extra storage and backups) from your live catalogue.
3. Your customer orders. They choose their options on the order form and pay. When Blesta activates the service the instance is launched in your account, with its own firewall and SSH key.
4. You get paid, they manage it. Blesta keeps billing as usual. Upgrades to another instance type resize the same server, keeping its disk and data.

What you get in Blesta

Selling and pricing

• Order options generated from your live AWS offerings: region, instance type, operating system, extra storage and backups you can keep. Options are created without prices, and you set each one under Packages, Configurable Options
• Choose which options customers see; anything you hide is fixed to your package's setting, and changing what is shown keeps every price
• Curated operating system families plus your own images
• A root disk size, extra storage at checkout and a startup script that runs on first boot, set per package
• Every package field carries guidance beside it, so setup needs no manual
• More than one AWS account if you need them

Provisioning you can trust

• Orders whose instance type, image and region AWS cannot build together are refused before anything is created, with the reason shown to you
• A failed create leaves nothing behind at AWS, and you can run Create again once the cause is fixed
• A server is never placed on your account's shared firewall: if its own cannot be created, provisioning stops and tells you which permission to add
• Data-preserving resizes: the server is stopped, resized and started again with its disk intact, and a size AWS refuses leaves it as it was, running
• Windows servers are treated as Windows throughout, with an RDP-ready firewall and the Administrator password shown on the service page

Running it day to day

• Clients and Services: every instance with the client paying for it, its type, region, IP and last recorded state
• The Products screen shows each package's server, settings, order options, catalogue state and the next step to go live
• Logs of every launch, start, stop, terminate, backup, resize and IP action across all services

What your customers get

• Start, stop and reboot, with a confirmation and a progress indicator, and a page that refreshes to the new state
• Connection details: public and private IP and a ready-to-paste ssh command, with a downloadable key for Linux servers that only the owner can fetch
• An in-browser terminal to their Linux server with no SSH client and no key handling (you switch it on, per package)
• Backups of the whole server, restored in a click, up to the number they bought, plus optional daily automatic backups with the retention you set
• A firewall they manage themselves: add or remove rules by protocol, port or range, and source
• Extra storage disks they add, grow or remove, attached to the server automatically
• A dedicated IP they can assign or release from their connection details
• Their own SSH keys, added by name and applied when the server is built or reinstalled
• Reinstall with a fresh copy of the original operating system, confirmed by typing the server's hostname, keeping the IP and extra disks
• Usage graphs for CPU and network in and out
• A start and stop schedule on the days and times they choose, if you allow it
• Recent activity in plain words, each action once, with its 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 Linux server ships with its own SSH key, and only the signed-in owner of a service can download it.
• The in-browser terminal is off until you switch it on. Sessions are short-lived and single-use, and the server's key never reaches the browser.
• The IAM policy we provide covers the EC2 actions the module uses. It applies to every resource in the account, so use an AWS account dedicated to reselling if you want the key fenced off.

One product, every feature

PD AWS EC2 is one paid module with everything included: provisioning, power, backups, firewall, volumes, metrics, resizes and the browser console. There is no free tier or add-on 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 being served, and only after that do customer features pause, behind a neutral "contact support" message that never mentions licensing. The browser console stops once the subscription has expired, and new servers are no longer provisioned, but everything already running stays up in your AWS account throughout.

Requirements

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