Connect an AWS account so PD Object Storage can provision customer buckets and scoped credentials on Amazon S3.

Prepare the intended AWS credential

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 AWS administrator to provide an access key with the required S3 bucket and object-management permissions, IAM user/policy/key management and CloudWatch GetMetricStatistics and ListMetrics permissions for usage collection. A credential that can list buckets does not establish that it can create customer IAM credentials or configure a new bucket.

Save and associate the connection

1. Open System Settings → Products/Services → Servers.
2. Add a server of type PD Object Storage.
3. Enter the AWS Access Key ID in Username and Secret Access Key in Password.
4. Save and place this connection in its own intended server group.
5. On the product’s Module Settings, save Amazon S3 as its Backend and select that group.
6. Review the product’s Default region / data location.

Hostname is not the AWS connection endpoint field here. Do not paste a customer bucket key or a Console password into the host connection.

Interpret Test Connection

Open PD Object Storage → Settings → Test Connection and inspect the named account result. The AWS test lists buckets; it creates no bucket or IAM user. It does not prove every provisioning, IAM, storage-setting or metric-read permission.

For a refusal, retain the account label, original time and redacted action/error for the administrator. Avoid replacing a working key or granting broad access merely because one operation was refused. Use the product guide after the connection and its backend association are saved.

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