Remove an extra bucket that is no longer required, after checking its contents and application use. PD AWS S3 does not allow the client to delete the primary bucket while the service exists.

Check that the bucket is empty

Identify the exact service and full bucket name. Stop applications writing to that bucket and preserve any data you intend to keep.

A bucket can look empty in a current-file listing while retaining object versions, delete markers or unfinished uploads. Have the storage administrator inspect those where necessary. Do not permanently remove versions merely to clear a warning if they are still needed for recovery.

Remove only the intended extra bucket

1. Open the service’s Buckets page.
2. Select the intended non-primary bucket’s delete action.
3. Type its full bucket name exactly as requested.
4. Read the confirmation and complete the removal only when intended.
5. Refresh the list and check the actual result with the responsible storage administrator where needed.

Deletion requires an empty bucket. A nonempty-bucket refusal is not an instruction to purge the entire service. A successful removal also means applications still configured for that name need a new destination.

Reconcile a failed or uncertain result

Read Activity and inspect actual native bucket existence before repeating the request. A row disappearing from the module is not by itself proof that AWS deleted the bucket. Retain the intended bucket, original time and exact redacted error while your hosting team checks the actual outcome, without keys or object contents.

Use the versioning guide for retained versions and the service purge guide only when the deliberate task is permanently removing a terminated service’s entire storage.

Check the bucket removal result

Your hosting team should confirm the exact additional bucket, service relationship and typed confirmation separately from an empty current-file listing. Your AWS administrator should inspect retained versions, delete markers, unfinished uploads and actual native bucket existence where needed, after deciding which data must remain. A refused existence check or a disappearing module row is not proof of AWS deletion. Inspect bucket and IAM-scope state after an uncertain request before retrying.

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