PD AWS MariaDB for Blesta

PD AWS MariaDB lets a hosting company sell managed MariaDB databases as its own package. Your customer orders in your Blesta order form, a dedicated MariaDB instance is built on Amazon RDS in your AWS account, and your customer runs it from their Blesta service page: 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 whose customers ask for MariaDB by name, for a CMS, a shop or an application that already speaks it, and who want to answer with a package instead of a support ticket.

Why hosts choose PD AWS MariaDB

MariaDB on its own terms. This module sells MariaDB on Amazon RDS and nothing else. Lightsail databases run only MySQL and PostgreSQL, so Lightsail is never offered here and your packages never promise something AWS cannot deliver. The customer sees a ready-to-paste mariadb command, not a generic one.

Graviton plans, priced by you. One click creates a package option group with five plans from Micro to X-Large on AWS's Graviton processors, from db.t4g.micro to db.m6g.xlarge, beside billable storage, region and version choices. The MariaDB versions offered are the ones AWS currently offers in your region. Every choice starts at no extra charge and you set the prices.

Every customer is isolated. Each order gets its own instance, its own master credentials and its own firewall group. Nothing is shared, even with another installation using the same AWS account, and the module refuses to take over a database it did not create.

Changes made safely. A snapshot is taken before a plan or storage change is applied, so a restore point exists. Storage is only ever grown, online; a downgrade never shrinks a database.

Failures are visible, not silent. If AWS refuses an order, or your key lacks a permission, the real reason is recorded for you and the customer is never left waiting on a database that is not coming. Running setup twice never creates a second instance.

Nothing left billing. Terminating a service deletes the database with its backups, its snapshots and its firewall group straight away. A host who wants a copy keeps one in the AWS console first.

How it works

1. Connect your AWS account. In Blesta, open Settings, Company, Modules, and add an account with your access key. The secret is stored encrypted. Test Connection, in the PD Modules panel, makes one read-only call and creates nothing.
2. Create your package. Add a Blesta package, choose PD AWS MariaDB as its module, and set region, plan, storage and MariaDB version. Press Generate plans to create the option group customers pick from.
3. Your customer orders. Once the order is paid, the instance is built in the region and size they chose, usually within a few minutes. Their service page says so, then fills in with the connection details by itself.
4. You get paid, they manage it. Blesta keeps billing as usual, and suspend, unsuspend and cancel follow your normal billing.

What you get in Blesta

Selling and pricing

• A package option group generated from the live AWS catalogue: region, plan, storage, high availability, public access and MariaDB version
• Prices set by you under Packages, Package Options
• Storage as a billable choice, from 20 GB
• A "High availability (Multi-AZ)" choice that gives the customer a standby in a second zone, and a public-access choice that is still limited to the addresses the customer allows
• Choices you do not offer are fixed to the package's own setting
• Sync with AWS hides choices AWS has retired and adds new ones, without touching prices or existing customers
• Billing stays yours: the service is charged at the prices of the package and its options, and nothing is metered into Blesta

Provisioning you can trust

• Plan upgrades resize the instance in place and keep its data; Multi-AZ is switched on or off in place
• 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 keeps it stopped, even though AWS restarts stopped databases after seven days; the customer cannot start it while suspended

Running it day to day

• Clients & Databases, in the PD Modules panel, lists every database with its service, plan, region, endpoint and live state
• An activity log of provisioning, resizes, snapshots and password resets across every service
• 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 recent provisioning activity, with no way to create, resize, delete or restore anything

What your customers get

• Start, stop and reboot, 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 weak password refused before anything is queued
• Connection details in one window with copy buttons, the password masked until revealed, and the Amazon certificate bundle with the exact client flag
• A firewall of allowed IPv4 addresses and ranges for the database port, applied on the next scheduled run
• Usage graphs for CPU, connections, freeable memory and free storage over the last 24 hours, from AWS's own metrics
• Snapshots they take and delete themselves, with the automated daily backups, kept seven days, listed beside them
• Activity in plain words, with the time and outcome of each action

Snapshots, Firewall, Connection details and Usage graphs are each a setting on the package. Turn one off and it disappears from the customer's page, and the request is refused however it is made. The pages render in Blesta's client portal and follow its theme, 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 are stored encrypted in Blesta 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.
• Only the database's own port is ever opened, and only to the addresses the customer lists.
• Restores stay with you: customers take and delete snapshots, and you restore from the AWS console when asked.

One product, every feature

PD AWS MariaDB 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. Each order creates a real, billable AWS resource, so there is no free trial.

If your subscription ever lapses, customers' databases are never touched or deleted. 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. Renewing restores everything at once.

Requirements

• Blesta 6 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
• PD Modules, the free control panel every PD module installs into