> 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

Frequently asked questions about Object Storage: what it is, buckets and objects, S3 access and clients, and data protection.

Each answer links to the concept, guide, or reference where the detail is.

<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 is used for.</td><td><a href="https://docs.plenit.com/docs-en/productos/object-storage/concepts/what-it-is.md">What is Object Storage?</a></td></tr><tr><td><strong>Buckets and objects</strong></td><td>How the data is organized, versioning, immutability, and automatic deletion.</td><td><a href="https://docs.plenit.com/fr/productos/object-storage/concepts/buckets-and-objects.md">Buckets et objets</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="https://docs.plenit.com/docs-en/productos/object-storage/concepts/s3-access-users-and-credentials.md">S3 access: users and credentials</a></td></tr><tr><td><strong>Data protection</strong></td><td>Durability, encryption, and data residency.</td><td><a href="https://docs.plenit.com/docs-en/productos/remote-desktop/concepts/backup-and-data-protection.md">Backup and Data Protection</a></td></tr></tbody></table>

### What it is

<details>

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

It is a high-capacity, S3-compatible storage space 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?](https://docs.plenit.com/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 via the web or a network drive. Object Storage is for storing large volumes, accessed by software via 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 commonly used for?</summary>

As a backup target 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 are the data organized?</summary>

In repositories (buckets) that contain objects. An object is data together with its associated information, stored as a unit. The organization is flat: objects are identified by their name, and the prefixes in that name act as "folders" when you need them. More in [Buckets and objects.](https://docs.plenit.com/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 previous state if something is overwritten or corrupted. It is especially useful when the repository receives automatic backups that are rewritten. The detail is in [Versioning and immutability.](https://docs.plenit.com/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 under development, 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 deleted after a period, so the repository does not grow 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; the rest must specify the repository name when configuring access. The data and commands are in [S3 credentials and access.](https://docs.plenit.com/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.](https://docs.plenit.com/docs-en/productos/object-storage/details/compatible-clients.md)

</details>

<details>

<summary>Can I have multiple users with different access levels in a repository?</summary>

Yes, a repository can have several S3 users, each with their own credentials and access level. You can create, enable, or disable them without deleting them, and rotate their keys. The recommendation is one credential per service or per client, with minimum privileges, so you can revoke or rotate one without affecting the rest. More in [Users and permissions.](https://docs.plenit.com/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 replica (three disks on 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.](https://docs.plenit.com/docs-en/productos/object-storage/details/encryption-and-compliance.md)

</details>

<details>

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

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

</details>

<details>

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

The region determines where the data reside, which is key for sovereignty and compliance requirements, and you choose it when activating the service. We confirm the available regions with the current platform before publishing them. The quota is configurable and can be increased as the volume grows, without recreating the repository. More in [Quota and regions.](https://docs.plenit.com/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="https://docs.plenit.com/docs-en/productos/object-storage/quickstart.md">Quick Start</a></td></tr><tr><td><strong>Concepts</strong></td><td>Understand the service design decisions.</td><td><a href="https://docs.plenit.com/docs-en/productos/object-storage/concepts.md">Concepts</a></td></tr><tr><td><strong>How-to</strong></td><td>Step-by-step guides for working with object storage.</td><td><a href="https://docs.plenit.com/docs-en/productos/object-storage/how-to.md">How-to</a></td></tr><tr><td><strong>Details</strong></td><td>S3 access, clients, and protection.</td><td><a href="https://docs.plenit.com/docs-en/productos/object-storage/details.md">Details</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 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/faq.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.
