Use PD MinIO S3’s lifecycle controls to expire matching current objects after a chosen age. These bucket rules are separate from retention after cancelling or terminating a service.

Review the full existing rule set

Open Storage settings, select the intended bucket and inspect all existing lifecycle rules. Saving replaces the complete configuration, so preserve every required rule before changing one. Clearing the list removes that configuration.

Decide the object prefix and expiration age carefully. A blank or broad prefix can match more files than intended. Complete any required recovery copy before enabling destructive cleanup.

Save supported expiration rules

1. Add or edit the intended rule and its matching prefix.
2. Set its current-object expiration age.
3. Review the enabled rules together and remove unintended matches.
4. Save once and reopen the bucket settings to verify the complete list.
5. Inspect later results rather than expecting immediate deletion when saving.

Use the controls actually offered on this backend. The module does not expose a standalone unfinished-upload cleanup rule or native remote-tier configuration as a customer task.

Keep versions and server cleanup separate

Current-object expiration in a versioned bucket can add a delete marker while leaving previous versions stored. It is not a rule to remove all historical versions or a complete way to reclaim versioned quota.

MinIO’s own background cleanup of unfinished uploads is a server-administrator concern. Do not shorten object expiration just to solve a stalled-upload problem.

For a failed save, retain the prior rule list, original time and redacted result while your hosting team checks the saved configuration. Do not submit an empty replacement repeatedly or treat the cancellation-retention window as a backup of already-expired objects.

Check the saved lifecycle rules

Your hosting team should compare the selected bucket, prior complete rule set, intended prefixes/ages and reopened configuration with the original save result. Saving replaces the configuration; an empty list clears it, and the MinIO controls expose current-object expiration rather than a full historical-version cleanup policy. Review an overly broad prefix and required recovery points with your storage administrator before further changes. Do not repeatedly submit an empty replacement or shorten object expiration to repair multipart-upload cleanup.

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