Create another bucket within a PD MinIO S3 service when its plan and host-enabled controls allow it. The extra bucket uses the service’s scoped connection credential.

Create the intended bucket

1. Open the service’s Buckets section.
2. Check the maximum allowance, including the primary bucket.
3. Enter the requested label and confirm creation.
4. Inspect the resulting list and exact generated bucket name.
5. Select that bucket explicitly in the application that should use it.

The module updates the service’s bucket scope. Do not guess the final name from the label or substitute a bucket from another service. Adding a bucket does not increase the plan’s total storage allowance.

Check its settings separately

A primary bucket’s versioning choice is not proof that every extra bucket has the same setting. Open Storage settings, select the new bucket and verify its actual versioning state before relying on historical recovery.

Review cleanup rules per bucket as well. Creating a new bucket does not copy a different bucket’s lifecycle policy. Use the versioning guide and cleanup guide for those separate changes.

Keep uncertain creation from becoming duplicates

If a request times out or fails, inspect Buckets and Activity before submitting another label. A bucket can exist even when a later permission or scope update failed.

Retain the service, requested label, original action time and redacted error while your hosting team checks an uncertain result. Removing an extra bucket is a separate deliberate task; use the deletion guide rather than terminating the service to reset it.

Check the additional bucket

Your hosting team should compare the intended service, bucket allowance and original requested label with the actual generated bucket name, service list and Activity result. Bucket creation can succeed before a later scope update fails; inspect the actual deployment with your storage administrator before adding another label. Check versioning and lifecycle on the new bucket separately from the primary bucket’s defaults. Do not terminate the service or remove another bucket to reset an uncertain creation.

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