Most hosting companies already have an AWS account. Few sell much from it. It's usually a server or two for their own systems, while customers who want "something on AWS" get pointed at the AWS console and told to get on with it.
AWS can be a whole product range in WHMCS instead: virtual servers, managed databases, object storage, DNS and SMS, each under your brand, on your invoices, at your prices. The customer pays you, you pay AWS, and the customer never needs an AWS login.
This post maps what's worth selling, the groundwork they all share, and the AWS charges that quietly turn a profitable service into a loss. Later posts in this series go deeper on each product.
What you can sell
| Product | AWS service | Who buys it |
|---|---|---|
| Simple VPS | Amazon Lightsail | Customers who want a server with a simple monthly price |
| Cloud server | Amazon EC2 | Customers who want instance types, Windows, or more control |
| Relational databases | Amazon RDS (MySQL, MariaDB, PostgreSQL, Oracle, SQL Server); MySQL and PostgreSQL also on Lightsail | Anyone with an app that needs a database they don't have to run |
| Document, graph and cache | Amazon DocumentDB, Neptune, ElastiCache | Developers whose apps already run in AWS |
| Object storage | Amazon S3 | Backups, media, static files |
| DNS hosting | Amazon Route 53 | Every customer with a domain |
| SMS | Amazon SNS | You, to text customers about invoices, services and tickets |
Two of these need a word of warning before you list them:
- DocumentDB, Neptune and ElastiCache are only reachable from inside your AWS network (the VPC). They have no public address, so they suit customers whose application servers sit in the same AWS network. Sell them to that audience, and say so on the product page, or you'll get refunds from customers who can't connect from their laptop.
- Oracle and SQL Server on RDS can be bought licence-included, so neither you nor the customer buys a separate licence. The licence is in AWS's hourly rate, so these cost noticeably more per hour than the open-source engines. Price them accordingly.
The groundwork they share
A dedicated IAM user per product, not your root key. Create an IAM user for each product line with only the permissions that product needs (Lightsail actions for the Lightsail product, RDS for databases, and so on). If a key ever leaks, the damage is limited to that product and you can revoke that key without touching anything else.
Store credentials where customers can't see them. In WHMCS the natural home is a server record, which WHMCS stores encrypted. Customers only ever see their own resource.
Turn on automatic setup. On the product's Module Settings tab, Automatically setup the product should normally be When the first payment is received. If it's off, an order completes, the service is marked Active, and nothing is ever created at AWS. There's no error anywhere; the customer simply has an empty service.
Choose regions on purpose. Not every plan, instance class or engine exists in every region. Generate your order-form options from what AWS actually offers per region, rather than typing lists by hand, and recheck them when AWS retires something.
Where the bill hides
This is the part that decides whether reselling AWS makes money.
Stopped isn't free.
- A stopped Lightsail instance or database is still billed. AWS says plainly that Lightsail resources accrue charges until they're deleted, stopped or not.
- A stopped EC2 instance stops charging for compute, but its disks (EBS volumes) and its public IPv4 address keep billing.
- A stopped RDS, DocumentDB or Neptune database stops charging for the instance, but not for storage, and AWS starts it again by itself after seven days so it doesn't miss maintenance. A database you "parked" for an unpaid invoice is quietly billing again a week later.
So suspension (stop the resource, keep the data) is the right reaction to a late payment, but it isn't a long-term state. Services that stay unpaid should be terminated.
Termination has to remove everything. A server is rarely alone. EC2 brings an Elastic IP, a security group, a key pair, extra volumes and backups; Lightsail brings snapshots and static IPs; a database brings snapshots and its firewall rules. Delete only the main resource and the rest keeps billing, with nobody paying for it.
Snapshots cost money for as long as they exist. If customers can take them, cap how many, or sell extra snapshot slots as a configurable option.
Usage-based products need metering. S3 storage and SMS are paid per use. If WHMCS doesn't know how much a customer used, you can't bill overage, and a single heavy user eats the margin of everyone else.
Margins drift. A customer upgrades and the price is never revisited. AWS changes a rate. A resource from a cancelled order is still running. None of this shows up in WHMCS. Once a month, compare the AWS bill with what each service actually pays you.
A sensible order to launch in
- Lightsail VPS. Predictable AWS cost, easy to price, easy to explain.
- Managed MySQL or PostgreSQL. The most common add-on a VPS customer asks for.
- S3 storage. A natural upsell for backups.
- Route 53 DNS. Low effort, useful to every customer.
- EC2, the other database engines and SMS, once the first products run smoothly.
The modules we built for this
We make a WHMCS module for each of these: PD AWS Lightsail, PD AWS EC2, PD AWS MySQL, MariaDB, PostgreSQL, Oracle and SQL Server, PD AWS DocumentDB, Neptune and ElastiCache, PD AWS S3, PD AWS Route 53 DNS and PD AWS SNS.
They're built around the traps above:
- terminating an EC2 server also releases its Elastic IP and removes its security group, key pair, extra disks and backups; DocumentDB and Neptune remove the cluster, its firewall and its snapshots;
- Lightsail and EC2 check daily for plans and images AWS has retired;
- S3 usage is metered into WHMCS each day, and a terminated S3 service keeps its data for a retention window you choose before anything is purged;
- Lightsail and EC2 show AWS's price for each plan next to a suggested price at your margin.
Every one installs and updates from a single panel inside WHMCS, the free PD Modules panel, and an update that fails rolls itself back. PD Cloud Cost & Margin reads your AWS bill and matches each charge to the WHMCS service that should be paying for it.
The PD AWS Lightsail module page is a good place to start. Questions about selling AWS from WHMCS are welcome in the comments.
PD Modules is made by Projektif Digital Ltd, the team behind PD Hosting.