Use per-bucket lifecycle rules to expire selected current objects and clear unfinished multipart uploads. Review the prefix and retention intent carefully: saving the rule set changes the bucket’s native cleanup configuration.

Review the complete rule set

Open the intended service’s Storage settings → Automatic clean-up controls and select the bucket. Read all current rules before editing. Saving replaces the set represented by this builder, and saving no rules clears the configuration; do not treat it as adding one isolated rule alongside every native custom setting.

1. Choose a descriptive rule and its intended prefix, if any.
2. Set Delete after (days) for current-object expiration where required.
3. Set Unfinished uploads (days) where that cleanup is intended.
4. Review the full list and enabled states.
5. Save and read back the resulting rules.

The module initially prepares unfinished-upload housekeeping when creating a bucket. Replacing or clearing lifecycle configuration can change that protection, so preserve the intended housekeeping rule when reviewing the complete set.

Keep versioning effects separate

Current-object expiration in a versioned bucket can create a delete marker and retain earlier versions. The builder does not offer noncurrent-version expiry or storage-class transitions, even though AWS supports wider native lifecycle policies.

Do not expect a saved current-object expiration rule to remove all stored versions or empty the bucket immediately. Use the versioning guide and an administrator-reviewed native policy where more advanced behaviour is needed.

Verify after saving

Check the correct bucket, prefix and actual stored rules. Lifecycle processing is separate from the moment the form saves. Keep a recovery copy before allowing intended expiration, and investigate a refused save before submitting an empty replacement.

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