Define the storage service customers can order through PD MinIO S3. Connect the intended MinIO server first, then choose the offering’s defaults and provisioning policy.

Configure the offering

1. Open Packages → Packages → Add Package.
2. Select PD MinIO S3 and the intended module account.
3. Review the package’s quota mode, default quota, maximum buckets, default versioning and client controls.
4. Set the name, pricing and package group, then save.
5. Add the package group to the intended form under Packages → Order Forms.

The default quota, bucket allowance and versioning describe new storage. Exposed customer choices can override those defaults. Use the option guide to review what is offered and priced.

Confirm that activation created storage

Paid orders need the Provision Paid Pending Services task under Settings → Company → Automation, the applicable client group’s Automatically Provision Paid Pending Services setting and a running cron. Staff activating a pending service must keep Use module enabled. Check Clients & Storage and Activity after provisioning runs.

Creating a service creates real storage resources on your deployment. Review the account and configuration before using your controlled provisioning process. Do not create repeated orders just to investigate an empty service record.

Check the client result

Confirm that the intended service has its primary bucket and service-specific connection details. Review the client bucket, share-link and storage-setting controls against what the plan includes. Never give a customer the host’s administrative key.

If provisioning remains pending or fails, follow the provisioning checks. A working billing record is separate from a usable bucket and verified customer credentials.

See the PD MinIO S3 Blesta guide for related tasks, or explore the module.