> 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

Object storage does not organize data into folders, but into repositories that contain objects. Understanding this difference is the basis 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 |
| Bucket (repository) | The container where objects live                                                           |

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

### Versioning

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

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

### Immutability

> #### 🚧 Object Lock is evolving
>
> Immutability allows objects to be locked so they cannot be deleted or modified during a period. 
>
> It is a capability 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. {/\* exact lifecycle deletion mechanism to be validated \*/}

### Where to go next

* How the software accesses the repository: [S3 access: users and credentials.](/docs-en/productos/object-storage/concepts/s3-access-users-and-credentials.md)
* How the data is protected: [Resilience and security.](/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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.plenit.com/docs-en/productos/object-storage/concepts/buckets-and-objects.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.