Connect your own AWS account so PD AWS S3 can provision storage for customers. The host’s AWS connection is separate from the restricted storage credentials issued for each customer service.

Prepare the intended AWS credential

Install PD Modules, connect the account holding your licence and install PD AWS S3 from the Store. Ask the AWS administrator to prepare a dedicated IAM credential for the intended bucket management, customer IAM users and keys, and CloudWatch usage reads. Keep the secret private and use the intended scope rather than root credentials.

Have the administrator validate policy actions against AWS’s S3 permissions reference. API operation names and IAM permission names can differ: CORS management uses s3:GetBucketCORS and s3:PutBucketCORS, while removing lifecycle configuration uses s3:PutLifecycleConfiguration. Do not expand to unrestricted access to silence a refused action.

Save the billing-platform connection

Open Settings → Company → Modules, find PD AWS S3 under Installed and choose Manage. Add an account with its name, Access Key ID and Secret Access Key, then save. This module account is used by packages. When editing later, an unchanged blank credential field retains its saved value; enter the replacement when rotating it.

Open PD AWS S3 → Settings → Test Connection. Inspect each configured account’s result before selecting it for orders.

Understand what the test proves

The test reads the S3 bucket list, a small IAM user list and CloudWatch metric listings. It does not create an IAM user, provision a bucket or prove every write, metric-data read and bucket-setting permission.

For a failure, retain the named AWS service, refused action and redacted result. When replacing the host credential, save the new pair, test and check the intended operation before retiring a shared old key. Never distribute this host credential to a customer; use the service connection guide for customer tools.

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