Use PD Cloudflare R2’s Buckets section to manage extra buckets belonging to the same storage service. Enable bucket management on the offering and confirm that the plan allows more than the primary bucket.

Create an extra bucket

1. Open the intended storage service and its Buckets section.
2. Check the plan’s maximum bucket allowance, including the primary bucket.
3. Enter the requested label and confirm creation.
4. Wait for the result, then check the actual generated bucket name in the list.
5. Configure the application to use that name with the service’s connection details.

The module manages the generated name and updates the service token’s bucket scope. Do not guess the final name from the label or substitute a bucket belonging to another service. The extra bucket shares the service jurisdiction; a regional placement hint is not necessarily repeated.

Delete only the intended empty bucket

Move or recover required files first. Select the extra bucket, type its exact name when requested and review the confirmation. A typed confirmation reduces mistakes; it cannot undo deletion.

The normal extra-bucket delete action expects an empty bucket. If the provider refuses a nonempty bucket, inspect its remaining objects and unfinished uploads through the responsible storage administrator. Do not terminate the entire service or use its purge control merely to remove one extra bucket.

Check the final scope

Confirm the deleted bucket has left the list and that remaining applications still access their intended buckets. The primary bucket is protected from this extra-bucket delete action. Deleting it is not a supported shortcut for resetting a service.

If creation or deletion has an uncertain outcome, inspect the list and Activity before retrying. Compare the reported outcome with the requested operation; keep credentials and file contents out of shared screenshots.

See the PD Cloudflare R2 WHMCS guide for related tasks, or explore the module.