PD AWS MySQL for WHMCS

PD AWS MySQL lets a hosting company sell managed MySQL databases as its own product. Your customer orders in your WHMCS cart, a dedicated MySQL database is built in your AWS account, and your customer manages it from your client area: connection details, usage graphs, snapshots and a firewall, with no AWS console and no AWS login. You set the price, AWS bills you its cost, and the difference is your margin.

It is built for hosts who want a database line that sits beside their hosting plans, without building a control panel, without handing out AWS access, and without a ticket every time a customer needs a snapshot or has changed office IP address.

Why hosts choose PD AWS MySQL

A real MySQL server for every customer. Each order gets its own database instance, its own master credentials and its own firewall group. Nothing is shared between customers, not even with another installation that uses the same AWS account. The module also refuses to take over a database it did not create, so a database someone made by hand in your account is never adopted, managed or deleted.

Two ways to sell it, under one product line. Back a product with Amazon RDS for resizable, firewalled plans with optional high availability, or with a flat-priced Lightsail database for an entry-level offer. You can mix both, and the customer's page adapts: Lightsail databases show no firewall section, because they have none.

Your customers choose, and you price every choice. One click builds the cart options from your live AWS catalogue: region, plan, storage, high availability, public access and MySQL version. The versions offered are the ones AWS currently offers in your region. Every option starts at no extra charge and you set the prices.

A database the customer can really use. Host, port 3306, database name, username and password are on the customer's page, each with a copy button, plus a ready-to-paste mysql command that connects over TLS and verifies the server with the Amazon certificate bundle, which is one click away. The password stays masked until the customer reveals it.

Failures are visible, not silent. If AWS refuses an order, or the AWS account lacks a permission, the real reason is recorded for you and the customer is never left staring at "still provisioning" for a database that is not coming. Running a setup twice never creates a second database.

Nothing left billing. Terminating a service deletes the database together with its automated backups, its snapshots and its firewall group.

How it works

1. Connect your AWS account. Add an access key once on a WHMCS server record. The secret is stored encrypted and never reaches a customer page. Test Connection makes one read-only call and creates nothing.
2. Create your product. Add a WHMCS product, choose the module on its Module Settings tab and switch on automatic setup. Set the backing service, region, plan, storage and MySQL version, then press Generate plans to offer choices at checkout.
3. Your customer orders. The database is built in the region and size they chose. While AWS builds it the customer's page says so, then fills in with the connection details by itself, usually within five minutes of AWS reporting it ready.
4. You get paid, they manage it. WHMCS keeps billing as usual. Suspend, unsuspend and terminate follow your normal billing.

What you get in WHMCS

Selling and pricing

• Cart options generated from the live AWS catalogue, linked to the product for you
• RDS plans from the burstable db.t3 and db.t4g sizes up to the Graviton db.m6g sizes, plus flat-priced Lightsail bundles
• Storage as a billable choice, from 20 GB on RDS
• A "High availability (Multi-AZ)" choice that gives the customer a standby in a second zone
• A "Publicly accessible" choice: switched off, the database is reachable only inside the AWS network; switched on, only from the IP addresses the customer allows
• Any option you hide is fixed to the product's own setting, so the product stays complete
• Sync with AWS hides options AWS has retired and adds new ones, without touching prices or existing customers
• A name prefix for new databases, such as db-10037, which applies to new orders only

Provisioning you can trust

• A paid order provisions with no admin step once automatic setup is on
• Upgrading the plan resizes an RDS database in place and keeps its data; turning Multi-AZ on or off is applied in place too
• A change that cannot be applied in place is reported to you as not applied, never accepted silently while the bill changes
• Suspend stops the database, and it stays stopped even though AWS restarts stopped databases after seven days. The customer cannot start it while suspended. Unsuspend starts it again with its data

Running it day to day

• Clients & Databases lists every database with its service, backing, plan, region, endpoint and live state
• An activity log across every service for provisioning, resizes, snapshots and password resets
• A report that checks your licence, the AWS SDK, and how many credential sets and databases you have
• Read-only assistant tools that report a service's database state and list recent provisioning activity, with no way to create, resize, delete or restore anything

What your customers get

• Start, stop and reboot from their own page, and a stopped database keeps its data
• Password reset with the engine's real rules stated on the form (8 to 41 characters), and a bad password refused before anything is queued
• Usage graphs for CPU, connections, freeable memory and free storage over the last 24 hours, drawn from AWS's own metrics
• Snapshots taken in one click and deleted by the customer; the daily automated backups, kept for seven days, are listed beside them
• A firewall of allowed IPv4 addresses and ranges, applied on the next scheduled run, with only the database port ever opened
• Activity in plain words: the last 40 operations with time and outcome
• Confirmation first for anything destructive, in a styled in-page dialog

Each of the Snapshots, Firewall, Connection details and Usage graphs pages is a switch on the product. Turn one off and it disappears from the customer's page, and the request is refused however it is made. You can also add your own text to the Overview, with the database name, status, host, port, region and plan filled in. The pages render natively on WHMCS's Six, Twenty-One and Nexus themes, and every word can be translated or reworded with override files that survive updates. Customers see only your brand.

Security built in

• Your AWS keys live on the WHMCS server record, stored encrypted, and never appear on a customer page, in a message or in a log.
• Database passwords are stored encrypted on the service, including one the customer sets with Reset password.
• The module never opens anything but the database's own port, and only to the addresses the customer lists.
• Your install is untouched: the module adds its own tables and templates, never modifies WHMCS files, and uninstalls without leaving orphans.

One product, every feature

PD AWS MySQL is one paid module with everything included. There are no tiers, no add-ons and no per-database fee from us: you pay AWS at cost and keep the margin. A managed database is a real, billable AWS resource from the first minute, so there is no free trial; price your plans with that in mind.

If your subscription ever lapses, your customers' databases are not touched. They keep running on your AWS account with their data. You get a 14-day grace period with everything working and a renewal reminder, then admin management locks while customers keep being served, and only after that do customer features pause behind a neutral "temporarily unavailable, please contact support" message that never mentions licensing. Renewing restores everything at once.

Requirements

• WHMCS 9 or later on PHP 8.2 or later, with the ionCube Loader
• An AWS account and an access key with the Amazon RDS permissions we list (plus the security group permissions every order needs, and Lightsail permissions if you sell Lightsail plans)
• PD Modules, the free control panel every PD module installs into