Use a customer service’s own PD MinIO S3 connection details to configure its backup, sync or storage application. Do not use the host’s administrative credentials.

Collect the service details

1. Open the intended storage service in the client area.
2. Review Information and Connection details.
3. Note the complete endpoint, exact bucket name, access key and secret privately.
4. Open Connect for the application’s suggested settings.
5. Confirm whether its form expects a complete endpoint URL or separate hostname and port.

The secret can be revealed again in the service controls; rotation is a separate change that invalidates the previous secret. Keep snippets containing credentials out of screenshots and tickets.

Configure and verify the destination

Choose an S3-compatible destination and use the issued API endpoint and service key pair. Enable path-style addressing where required. The module’s signing region is us-east-1; this is a connection setting, not a choice that moves data to another location.

Use a harmless test object to verify the operations the application needs. A successful upload does not prove a backup can be restored; test the relevant recovery path too. The service key is restricted to that service’s buckets and does not grant native bucket-administration controls.

Diagnose a refusal

Compare the full current key pair, endpoint, bucket and signing settings. For an upload-only refusal, inspect the actual access mode and quota status. For hostname or certificate failures, use the endpoint guide.

Retain the service reference, original operation time and redacted error while your hosting team checks the affected application and service. Never attach a secret, signed object URL or complete credential-bearing snippet.

Check the application connection

Your hosting team should compare the affected service’s current endpoint, bucket, complete issued key pair, path-style choice and signing region with the customer application’s intended settings. Keep the host administrative connection separate. Check access mode, quota and suspension when reads work but uploads fail, and inspect actual application/provider results before rotating a key. Use your controlled storage test process only where the intended object operation is authorised. Do not ask the customer to submit its secret, signed link or a credential-bearing snippet.

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