Remove an additional PD MinIO S3 bucket only when its data is no longer required. The normal bucket-delete action does not empty the bucket or purge the entire service.

Establish that it is the right empty bucket

Review the exact service and extra bucket name. Move or recover required objects first and verify the destination. A visually empty folder listing may still hide historical versions, delete markers or unfinished multipart uploads.

Use a version-aware view through the responsible storage administrator where needed. Do not assume ordinary deletion in a versioned bucket removed its stored history. Keep the primary bucket and unrelated service data out of this operation.

Use the extra-bucket delete control

1. Open the service’s Buckets section.
2. Select the intended additional bucket’s delete action.
3. Type its exact name when requested and review the confirmation.
4. Inspect the result and refresh the bucket list.
5. Verify the remaining applications still use their intended buckets.

Typed confirmation is a safety check; it cannot reverse deletion. The primary bucket is protected from this extra-bucket action.

Handle a refusal without escalating deletion

A nonempty or protected bucket can be refused. Preserve the exact error and have the storage administrator identify remaining versions, markers or unfinished uploads before deciding what to remove.

Do not approve the service’s Retention purge merely to remove one extra bucket. For an uncertain result, inspect the list and Activity before retrying. Retain the service, bucket, original time and redacted error while your hosting team checks the remaining state, without credentials or object contents.

Check the bucket removal result

Your hosting team should confirm the exact additional bucket, service association and typed confirmation, separately from whether its current-object list looks empty. Have your storage administrator review remaining versions, delete markers and multipart uploads where needed, after deciding which data must be kept. Inspect actual bucket and scope state after an error before retrying: deletion and the later scope update can fail at different stages. Do not use service Retention purge to remove one extra bucket.

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