Connect your own MinIO deployment as a PD Object Storage backend. Use its API address and an administrative credential that can manage the intended service users, policies, buckets and object settings.

Prepare the deployment connection

Install PD Modules, connect the account holding your licence and install PD Object Storage from its Store. Prepare a dedicated host credential for the intended account; customers receive separate service credentials. Keep host credentials out of customer tools, screenshots and tickets.

Ask the storage administrator to confirm the API hostname, port, trusted TLS certificate and required S3 and MinIO administration permissions. A plain S3 read/write user is not a substitute for the required administration API access. The browser Console address is separate from the API endpoint.

Save the server and backend

1. Open System Settings → Products/Services → Servers and add a PD Object Storage server.
2. Enter the API hostname in Hostname and intended API port in Port.
3. Enter the admin access key in Username and its secret in Password.
4. Enable Secure for HTTPS, save and review its server group.
5. Save MinIO as the product’s Backend and select that group.

For an HTTPS proxy on port 443, set Port 443 explicitly; a bare endpoint otherwise uses the module’s MinIO API-port default 9000. Keep certificate validation enabled. A private certificate needs the appropriate trust configuration or a trusted endpoint.

Check both APIs

Use PD Object Storage → Settings → Test Connection and inspect the account result. MinIO’s test reads administration server information and the S3 bucket list. It creates no user or bucket and does not prove every user, policy, bucket-setting or usage permission.

A hostname reachable from the billing server may still be unreachable from customer applications. Use the customer connection guide to check the issued destination separately, without sharing the admin credential.

See the PD Object Storage WHMCS guide for related tasks, or explore PD Object Storage.