Use the credentials issued for the customer’s PD AWS S3 service to connect an S3-compatible backup tool or storage client. Do not use your host’s AWS provisioning key in customer applications.

Read this service’s connection details

1. Open the intended storage service in the WHMCS client area.
2. Open Information and Connection details.
3. Note the endpoint, region, primary bucket, access key and addressing information.
4. Reveal the secret only when entering it into the intended private application settings.
5. Open Connect for the module’s tool-specific guidance.

Use the full generated bucket name, not a guessed label. The key is scoped to this service’s buckets; account-wide bucket discovery may be refused even when direct access to the intended bucket works.

Configure and verify the application

Choose the tool’s S3-compatible destination and enter the displayed endpoint, region, access key, secret and bucket. Follow the addressing choice shown by the service. The Connect guidance includes backup destinations and WordPress backup plugins where supported.

Use a small non-sensitive test file to verify upload and download, then check your application’s own restore process. The module supplies storage; it does not automatically schedule every application’s backups or prove they can be restored.

Diagnose a refused connection

Check the exact endpoint, bucket, region, current key and service access mode. An upload-only refusal can be a hard-quota pause, read-only suspension or application permission problem rather than a wrong password.

Keep credentials and storage links out of screenshots and tickets. After service key rotation, update every tool using the old pair. For browser uploads, use the separate CORS guide.

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