> 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/s3-access-users-and-credentials.md).

# S3 access: users and credentials

Access is not via username and password on a website, but through **the S3 protocol**: the software connects to the repository with credentials and operates on the objects.

That S3 compatibility is precisely what makes the service so versatile.

<figure><img src="https://3894148717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxksPMyYRDCe4qKkhbpcY%2Fuploads%2F25GsrmyUzdClmndOYQbS%2Fdiagram-object-storage-s3-access.png?alt=media&amp;token=0237fbb1-2c74-4094-9559-9ef428cf4c6e" alt="Diagrama de acceso S3: tu software se conecta con sus credenciales S3 por HTTPS al repositorio (bucket), donde los objetos están versionados y cifrados"><figcaption><p>The software connects to the repository via S3 with its credentials; the objects are encrypted and replicated</p></figcaption></figure>

### Users and credentials

Each access is identified with an S3 user, which has a pair of credentials: an access key and a secret key. This is what you configure in the software so it can read and write to the repository.

| Item       | What it is for                                            |
| ---------- | --------------------------------------------------------- |
| S3 user    | Identifies who or what is accessing the repository        |
| Access key | The public identifier of the credential                   |
| Secret key | The private part, which the software uses to authenticate |

> #### 🚧 Treat the secret key like a password
>
> The secret key grants access to the repository. Keep it safe, do not share it through open channels, and rotate it if you suspect it has been exposed. You can enable and disable credentials whenever you need to.

### Compatible clients and software

When speaking standard S3, the repository works with a multitude of tools without custom development: backup software, desktop clients, and command-line utilities. That is the great advantage of an open standard.

### Signed URLs

You can generate **temporary links** so that someone can download an object for a limited time, without giving them credentials or permanent access to the repository.

### Where to continue

* How what you store is organized: [Buckets and objects.](https://docs.plenit.com/docs-en/productos/object-storage/concepts/buckets-and-objects.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/s3-access-users-and-credentials.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.
