> For the complete documentation index, see [llms.txt](https://docs.plenit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.plenit.com/docs-en/productos/object-storage/concepts/buckets-and-objects.md).

# Buckets and objects

How the repository is organized, what an object is, and how versioning and immutability protect your data.

Object storage does not organize data in folders, but in repositories that contain objects. Understanding this difference is the foundation for using it well.

### Object and repository

| Concept             | What it is                                                                                 |
| ------------------- | ------------------------------------------------------------------------------------------ |
| Object              | A piece of data (a file) together with its associated information, stored as a single unit |
| Repository (bucket) | The container where objects live                                                           |

Unlike a disk with nested folders, organization here is flat: objects are identified by their name, and prefixes in that name serve as "folders" when you need them.

### Versioning

With versioning enabled, every time an object is overwritten, the previous version is preserved. This way, you can return to a previous state if something gets overwritten or corrupted.

> #### 📘 Versioning is your safety net against overwrites
>
> Without versioning, overwriting an object is permanent. With versioning, you can recover the good version.
>
> It is especially useful when the repository receives automatic backups that are rewritten.

### Immutability

> #### 🚧 Object Lock in progress
>
> Immutability allows objects to be locked so they cannot be deleted or modified for a period of time.
>
> It is a feature designed for retention and protection against ransomware. We confirm its availability and scope with the current platform before publishing the details.

### Automatic deletion

You can rely on rules so that objects that are no longer needed are deleted automatically after a while, so the repository does not grow uncontrollably. {/\* TO BE VALIDATED: exact mechanics of lifecycle deletion \*/}

### Where to follow

* How the software accesses the repository: [S3 access: users and credentials.](https://docs.plenit.com/docs-en/productos/object-storage/concepts/s3-access-users-and-credentials.md)
* How the data is protected: [Resilience and security.](https://docs.plenit.com/docs-en/productos/object-storage/concepts/resilience-and-security.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.plenit.com/docs-en/productos/object-storage/concepts/buckets-and-objects.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.
