Use the service’s Buckets page to add storage within its bucket allowance. PD AWS S3 keeps the new bucket in the same service scope and region; it is not a separate customer account.

Check the allowance

Confirm Client: Bucket management is enabled and the service has an unused Max Buckets allowance. The primary bucket counts towards that limit. The service must be in a state that permits management.

1. Open the intended service’s Buckets page.
2. Use the create-bucket control and supply a descriptive label.
3. Save and inspect the returned full bucket name.
4. Confirm it appears under this service.
5. Use that actual name when configuring the application.

The module generates the full name within its service naming scheme. Do not assume the label is the final AWS name or that it selects a different region.

Configure the new bucket deliberately

Review versioning, lifecycle and CORS on this bucket separately. Do not assume every primary-bucket setting was copied automatically. Check service usage across all its buckets when planning capacity.

Handle a refusal

Check the service state, bucket allowance and exact redacted result before repeating a creation request. A saved bucket can exist even if a later permission update failed, so reconcile the actual list and Activity first.

Use the extra-bucket removal guide for deletion. Do not terminate the whole service just to remove one empty additional bucket.

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