PD AWS S3 for WHMCS and Blesta

PD AWS S3 is available for WHMCS (8.13 or later) and Blesta (6.0 or later). Each has its own page with the screenshots, requirements and price for that system. A module is added to the PD Modules licence of the installation it runs on, so a WHMCS installation and a Blesta installation each hold their own licence.

Yours. You connect your own account, and every customer bucket is provisioned into it. You pay the provider at cost, set your sell price in WHMCS or Blesta, and keep the difference.

Every order gets its own bucket and an IAM user scoped to that bucket alone. One customer's credential cannot reach another's data, and your master credentials stay on your WHMCS or Blesta server — they are never sent to the customer or stored in the client area.

A daily task measures each service's real usage and writes it into WHMCS's or Blesta's disk-usage fields. Native overage billing, quota warnings and the client-area usage graph then work exactly as they do for hosting products — there is nothing extra to configure.

PD Object Storage is the flagship covering Amazon S3, Cloudflare R2, MinIO and DigitalOcean Spaces in one module. This edition is the same engine focused on Amazon S3 alone — choose it if that is the only backend you sell, and move up to the flagship if you later add another.

Nothing of yours is touched, and nothing is deleted. The module steps down in stages instead: a 14-day grace period where everything still works and you get a renewal reminder, then admin management locks while your customers carry on being served, and only after that do the customer-facing features stop — behind a neutral "temporarily unavailable, please contact support" message that never mentions licensing to your customer. Anything the module provisioned keeps running in your own account throughout, and your data and settings stay exactly where they are. Renewing restores everything immediately.