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

# S3 credentials and access

To connect any software via S3 you need four pieces of data.

The concept is in[ S3 access: users and credentials](/docs-en/productos/object-storage/concepts/s3-access-users-and-credentials.md); here you have the data and the commands.

### Connection data

| Field                    | What it is                              | Where you get it                       |
| ------------------------ | --------------------------------------- | -------------------------------------- |
| Endpoint                 | The repository access URL               | In the repository summary, bottom left |
| Repository name (bucket) | The bucket name, which acts as *path*   | In the repository summary, top left    |
| Access key               | The public identifier of the credential | In **users › (…) › Keys**              |
| Secret key               | The private part of the credential      | In **users › (…) › Keys**              |

> #### 📘 Owner and rest of users
>
> The repository owner user accesses directly, without specifying the repository. 
>
> The rest of the users must specify the **repository name** (the *path*) when configuring access, because they are not redirected automatically.

### AWS CLI

```shell
# Save credentials in a profile
aws configure
# AWS Access Key ID:     <CLAVE_DE_ACCESO>
# AWS Secret Access Key: <CLAVE_SECRETA>

# List repository contents
aws s3 ls s3://NOMBRE-REPOSITORIO --endpoint-url https://ENDPOINT

# Upload an object
aws s3 cp ./backup.tar.gz s3://NOMBRE-REPOSITORIO/ --endpoint-url https://ENDPOINT

# Download an object
aws s3 cp s3://NOMBRE-REPOSITORIO/backup.tar.gz ./ --endpoint-url https://ENDPOINT
```

### s3cmd

```shell
# Guided configuration: enter the keys and, as Host, your endpoint
s3cmd --configure

# Common operations
s3cmd ls s3://NOMBRE-REPOSITORIO
s3cmd put backup.tar.gz s3://NOMBRE-REPOSITORIO/
s3cmd sync ./carpeta/ s3://NOMBRE-REPOSITORIO/carpeta/
```

### rclone

```shell
# Create an "s3" type remote (provider: Other) with your endpoint and keys
rclone config

# Common operations (remote called "plenit" in this example)
rclone ls plenit:NOMBRE-REPOSITORIO
rclone copy ./backup.tar.gz plenit:NOMBRE-REPOSITORIO/
rclone sync ./carpeta plenit:NOMBRE-REPOSITORIO/carpeta

```

> #### 🚧 Take care of the secret key
>
> The secret key grants access to the repository. Don't leave it in the shell history or in plain scripts: use credential profiles or environment variables, and rotate it from **users › (…) › Keys** if you suspect it has been exposed. A different credential for each client or service makes it easier to revoke without affecting the rest.

### Signed URLs

To deliver a specific object without giving credentials, you generate a temporary download link.

| Aspect     | Detail                                                          |
| ---------- | --------------------------------------------------------------- |
| What it is | A temporary download link for an object                         |
| What for   | Share a specific object without giving access to the repository |
| Validity   | Expires after the time you define                               |

### Where to continue

* Which software you can connect: [Compatible clients.](/docs-en/productos/object-storage/details/compatible-clients.md)
* Who accesses and with what permissions: [Users and permissions.](/docs-en/productos/object-storage/details/users-and-permissions.md)
* The concept of users and credentials: [S3 access: users and credentials.](/docs-en/productos/object-storage/concepts/s3-access-users-and-credentials.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/details/credentials-and-s3-access.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.