> 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/faq.md).

# Frequently Asked Questions

Each answer links to the concept, guide, or reference where the details are.

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>What it is</strong></td><td>What the service is, how it differs from Files, and what it's used for.</td><td><a href="/pages/64df8a25f5532cd11cedb6bd7c719d54233f0b62">/pages/64df8a25f5532cd11cedb6bd7c719d54233f0b62</a></td></tr><tr><td><strong>Buckets and objects</strong></td><td>How data is organized, versioning, immutability, and automatic deletion.</td><td><a href="/spaces/dMHo74cNV9wuqavXFVq6/pages/66a9ea76f1529bf6e8171e43defa1c7602e34684">/spaces/dMHo74cNV9wuqavXFVq6/pages/66a9ea76f1529bf6e8171e43defa1c7602e34684</a></td></tr><tr><td><strong>S3 access and clients</strong></td><td>What you need to connect, what software is compatible, and users per repository.</td><td><a href="/pages/6a1f27590f01b3f2310f0defd7c9ee6f0f8b35b4">/pages/6a1f27590f01b3f2310f0defd7c9ee6f0f8b35b4</a></td></tr><tr><td><strong>Data protection</strong></td><td>Durability, encryption, and data residency.</td><td><a href="/pages/a4b9ab73ac06c4adcabd76e9dda3c64a51aac81e">/pages/a4b9ab73ac06c4adcabd76e9dda3c64a51aac81e</a></td></tr></tbody></table>

### What it is

<details>

<summary>What is Object Storage?</summary>

It is a high-capacity, S3-compatible storage room where you store large volumes of data: backups, application files, exports, and logs. It is not managed by folders like a disk, but by software that speaks S3. More in [What is Object Storage?](/docs-en/productos/object-storage/concepts/what-it-is.md)

</details>

<details>

<summary>How is it different from File Storage?</summary>

File Storage is for day-to-day work on files, accessed by people through the web or a network drive. Object Storage is for storing large volumes, accessed by software through the S3 protocol. The quick rule: if a person opens and edits it daily, it's Files; if software writes or reads it, it's Objects.

</details>

<details>

<summary>What is it usually used for?</summary>

As a backup destination with S3-compatible tools, archiving and retention of large volumes, application data and exports, logs and technical artifacts, and repositories for restoration and version preservation.

</details>

### Buckets and objects

<details>

<summary>How is data organized?</summary>

In repositories (buckets) that contain objects. An object is a piece of data together with its associated information, stored as a unit. The organization is flat: objects are identified by their name, and prefixes in that name play the role of "folders" when you need them. More in [Buckets and objects.](/docs-en/productos/object-storage/concepts/buckets-and-objects.md)

</details>

<details>

<summary>What does versioning do?</summary>

With versioning enabled, every time an object is overwritten, the previous version is preserved, so you can return to a prior state if something is overwritten or corrupted. It is especially useful when the repository receives automatic backups that are rewritten. The details are in [Versioning and immutability.](/docs-en/productos/object-storage/details/versioning-and-immutability.md)

</details>

<details>

<summary>Can I prevent an object from being deleted or modified for a period of time?</summary>

Immutability (Object Lock) is designed for that: it locks objects against deletion or modification for a period, useful for retention and protection against ransomware. It is a capability in progress, so we confirm its scope and availability with the current platform before publishing the configuration details.

</details>

<details>

<summary>Can I make expired objects be deleted automatically?</summary>

Yes, you can rely on automatic deletion rules so that objects that are no longer needed are removed after a while, preventing the repository from growing uncontrollably.

</details>

### S3 access and clients

<details>

<summary>What do I need to connect software via S3?</summary>

Four pieces of data: the endpoint (the access URL), the repository name (which acts as the path), the access key, and the secret key. The owner user accesses directly; everyone else must specify the repository name when configuring access. The data and commands are in [Credentials and S3 access.](/docs-en/productos/object-storage/details/credentials-and-s3-access.md)

</details>

<details>

<summary>What software can I connect?</summary>

Any S3-compatible client works, with no custom development: backup software (Veeam, Acronis, Bacula, Veritas, Ahsay), NAS (QNAP), desktop clients (Cyberduck, S3 Browser), and command line (AWS CLI, s3cmd, rclone). The S3 standard is the advantage: you use the tool you already have. More in [Compatible clients.](/docs-en/productos/object-storage/details/compatible-clients.md)

</details>

<details>

<summary>Can I have several users with different access rights in one repository?</summary>

Yes, a repository can have multiple S3 users, each with their own credentials and access level. You can create, activate, or deactivate them without deleting them, and rotate their keys. The recommendation is one credential per service or per client, with minimum permissions, so you can revoke or rotate one without affecting the rest. More in [Users and permissions.](/docs-en/productos/object-storage/details/users-and-permissions.md)

</details>

### Data protection

<details>

<summary>How is data durability protected?</summary>

Each object is stored in triple replication (three disks across three different servers), and at least one copy is kept in a different data center. The design is intended for very high data durability. More in [Resilience, encryption, and compliance.](/docs-en/productos/object-storage/details/encryption-and-compliance.md)

</details>

<details>

<summary>Is the data encrypted?</summary>

Yes, in transit over HTTPS and at rest in storage. On top of that, there are firewalls, IDS/IPS, and anti-DDoS protection at the perimeter, logical isolation for each customer, and S3 credentials that you control and rotate.

</details>

<details>

<summary>Where does the data reside?</summary>

The region determines where the data resides, which is key for sovereignty and compliance requirements, and you choose it when you sign up for the service. We confirm the available regions with the current platform before publishing them. The quota is configurable and expands as the volume grows, without recreating the repository. More in [Quota and regions.](/docs-en/productos/object-storage/details/quota-and-regions.md)

</details>

### Next steps

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Quick Start</strong></td><td>Deploy the repository step by step.</td><td><a href="/pages/f1f32869399abfae9c6aed12e99e2530914dbb5e">/pages/f1f32869399abfae9c6aed12e99e2530914dbb5e</a></td></tr><tr><td><strong>Concepts</strong></td><td>Understand the service design decisions.</td><td><a href="/pages/11e9ce24314b905961576b20ddc71fa744f80304">/pages/11e9ce24314b905961576b20ddc71fa744f80304</a></td></tr><tr><td><strong>How-to</strong></td><td>Step-by-step guides for working with object storage.</td><td><a href="/pages/d6280aa201f29f9e580e9bd8ca831d3b4dfb7344">/pages/d6280aa201f29f9e580e9bd8ca831d3b4dfb7344</a></td></tr><tr><td><strong>Details</strong></td><td>S3 access, clients, and protection.</td><td><a href="/pages/10c65d0940c792fee84844970283f91c32834864">/pages/10c65d0940c792fee84844970283f91c32834864</a></td></tr></tbody></table>


---

# 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/faq.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.