> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.ibee.co.in/docs/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.ibee.co.in/docs/_mcp/server.

# Lifecycle Management

> Create lifecycle rules in IBEE Object Storage to automatically delete objects, abort incomplete uploads, or transition objects to Infrequent Access storage after a set number of days.

A **lifecycle rule** is a recurring background job, attached to a bucket, that runs against the objects inside it. Use rules to automatically delete old data, clean up incomplete multipart uploads, or move objects to a lower-cost storage class. Rules are evaluated **daily** and applied automatically.

## Before you begin

* An active IBEE Solutions organization with a bucket ([Create a bucket](/docs/infrastructure/object-storage/buckets))

### 1. Open Lifecycle Policies

Open a bucket, click the **Settings** tab, then click the **Lifecycle Policies** tab.

### 2. Add a rule

Click **+ Add Rule**. If no rules exist yet, click **+ Create Your First Rule**.

![IBEE Object Storage lifecycle policies](/docs/_fern-img/431d498cfc0e96e5b07511cb0995f4e534c60defd53657dcfd4bca50b90476ef.webp)![IBEE Object Storage lifecycle policies](/docs/_fern-img/5edd9199f5b605a169bc18480bcee7879919f263e876aab122939ddb74b63e60.webp)

### 3. Configure the rule

Fill in the **Lifecycle rules** panel — subtitle: *"Automatically expire objects, clean incomplete uploads, or move data after a set period."*

| Field              | Type                            | Default | Description                                                                               |
| ------------------ | ------------------------------- | ------- | ----------------------------------------------------------------------------------------- |
| Prefix filter      | Text                            | —       | Placeholder `e.g. logs/`. Leave empty to apply this rule to all objects in the bucket.    |
| Rule status        | Toggle                          | Enabled | Enable or disable the rule. Disabled rules remain saved but are not executed.             |
| Expire after       | Checkbox + **Days** or **Date** | 30 days | Delete matching objects after a number of days, or on a specific date.                    |
| Incomplete uploads | Checkbox + days                 | 7 days  | Abort unfinished multipart uploads after the specified number of days.                    |
| Transition after   | Checkbox + **Days** or **Date** | 30 days | Move objects to a lower-cost storage class after a number of days, or on a specific date. |

Under **Lifecycle actions**, the helper text reads *"Select at least one action before applying changes."*

Click **Apply changes**.

> **Info**
>
> At least one lifecycle action must be selected before you can apply changes.

> **Info**
>
> **How lifecycle rules work**
>
> * Rules are **evaluated daily** and applied automatically.
> * Use a **prefix** to target specific folders (e.g. `logs/` or `temp/`).
> * **Disabled rules** remain saved but are not executed.

## Lifecycle actions

| Action             | Description                                                                                     | Unit         |
| ------------------ | ----------------------------------------------------------------------------------------------- | ------------ |
| Expire after       | Deletes matching objects after the specified period or on the specified date                    | Days or Date |
| Incomplete uploads | Aborts unfinished multipart uploads after the specified period                                  | Days         |
| Transition after   | Moves objects to a lower-cost storage class after the specified period or on the specified date | Days or Date |

## Troubleshooting

**Apply changes is disabled**
At least one lifecycle action (Expire after, Incomplete uploads, or Transition after) must be checked before applying changes.

**Rule is not executing**
Check that the **Rule status** toggle is set to **Enabled**. Disabled rules are saved but not executed.

**Rule applying to all objects unexpectedly**
If the **Prefix filter** field is empty, the rule applies to all objects in the bucket. Add a prefix to restrict scope.

## Related

* [Buckets](/docs/infrastructure/object-storage/buckets)
* [Bucket policies](/docs/infrastructure/object-storage/buckets/bucket-policies)
* [Pricing](/docs/infrastructure/object-storage/pricing)