Connect an S3-compatible tool to PD Object Storage in WHMCS
Configure a backup, sync or storage application with the customer service’s own connection details. PD Object Storage prepares backend-specific suggestions, but the application must use the issued destination and current credential pair.
Collect the intended service details
- Open the storage service in the WHMCS client area.
- Open Connection details from its storage overview.
- Note the exact bucket, endpoint and access key privately.
- Use Show or Copy for the saved secret.
- Open Connect and review the application’s suggested settings.
Showing the secret again does not require credential rotation. Keep filled-in snippets, secrets and signed links out of screenshots or support tickets. Never use the host’s administrative credential in a customer tool.
Match the application to the backend
Use the connection guide’s addressing and signing settings. MinIO commonly needs path-style addressing and the issued deployment endpoint. Spaces uses its regional endpoint and virtual-host style. AWS uses the bucket’s actual region. R2 uses its issued account/jurisdiction endpoint; its S3 signing region is auto.
An application may ask for a complete endpoint URL or separate host, port and TLS fields. Review its expected format rather than pasting a Console address or substituting a public download hostname. Different SDKs can distinguish endpoint placement from a separate validation-region setting.
Verify the workflow you need
Use a harmless test object and check the application’s required upload, download and recovery operations. An upload succeeding does not establish that a backup can be restored.
For a refusal, compare the current complete key pair, exact bucket, endpoint and service access mode. Check whether credentials were recently replaced. Use access troubleshooting if needed, supplying the operation time and redacted error without customer files or credentials.
See the PD Object Storage WHMCS guide for related tasks, or explore PD Object Storage.