> For the complete documentation index, see [llms.txt](https://docs.weka.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.weka.io/4.2/additional-protocols/s3/s3-information-lifecycle-management.md).

# S3 rules information lifecycle management (ILM)

This page describes how to manage information lifecycle (ILM) rules for S3 buckets.

For S3 buckets, you can set information lifecycle rules to apply to the objects within the bucket. The lifecycle rules apply to the data within the bucket, regardless of the protocol.

WEKA supports rules for expiring objects and enables you to set different expirations per object prefix and tags. WEKA supports up to 1000 rules per bucket. If multiple rules overlap, the rule with the earliest expiration that applies for an object deletes this object from the bucket.

**Related topics**

[Manage S3 lifecycle rules using the GUI](/4.2/additional-protocols/s3/s3-information-lifecycle-management/s3-information-lifecycle-management.md)

[Manage S3 lifecycle rules using the CLI](/4.2/additional-protocols/s3/s3-information-lifecycle-management/s3-information-lifecycle-management-1.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.weka.io/4.2/additional-protocols/s3/s3-information-lifecycle-management.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.