Review PD MinIO S3 retention before ending a storage service. Ending access and permanently deleting the stored objects are separate operations.

Set the intended policy

1. Open PD MinIO S3 → Settings.
2. Review Keep data after termination and its available period.
3. Review Purging terminated data, distinguishing Manual from Automatic.
4. Establish the recovery and approval process before applying the policy to real services.

Manual mode requires approval before eligible queue work can delete the retained storage. Automatic mode can approve deletion when its period is due. Delete immediately removes the retention delay; it does not turn a held manual approval into permission to delete.

Confirm what termination changed

Successful termination revokes the service’s native user/credential access while retaining its buckets for the selected policy. Inspect Activity and Retention for the actual result and deadline. The last stored usage sample is not necessarily an exact inventory taken at revocation.

Retained data is still the original storage, not an independent backup. Bucket lifecycle rules and deliberate native administrator actions can still affect its contents. Customers should obtain required data while their access still works; do not promise self-service downloads after credential revocation.

Decide recovery before deletion begins

Use recovery for the original retained service. If a purge has started, some objects may already be gone. Hold can stop later queue work but cannot reconstruct deleted data.

Use the purge guide only when permanent deletion of all storage associated with the terminated service is intended.

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