> 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/how-to/how-to-integrate-with-an-s3-client.md).

# How to Integrate Object Storage with an S3 Client

Connect your Plenit Object Storage to an S3 client in two steps: gather the connection details in the dashboard and configure them in the client.

Object Storage is designed to store large volumes of application data (archiving, backup, IoT, DevOps) through an S3-compatible API.

That lets you connect it to any S3 client (CyberDuck, S3 Browser or another one) to manage your buckets from your computer. This guide gathers the data from the panel and configures it in the client.

> #### 👍 What you get
>
> Your Object Storage bucket connected to an S3 client, ready to upload, download, and manage objects from the application.

### Before you start

* Access the administration panel at [admin.plenit.com](https://admin.plenit.com) with permissions on the service.
* Have an **Object Storage**. If you don't have one yet, set it up with the [Quick Start for Object Storage.](https://docs.plenit.com/docs-en/productos/object-storage/quickstart.md)
* Have an S3 client installed (for example, CyberDuck or S3 Browser) on your computer.

### Step 1. Collect the connection data in the panel

At [admin.plenit.com](https://admin.plenit.com), go to **Cloud Services → Object Storage** and enter the subscription. An API integration needs four pieces of data:

* **Endpoint (access URL)**: click Connect in the subscription and choose access via client. The window shows the service URL.
* **Path (bucket name)**: appears as Bucket in that same window.
* **Access Key**: in **Users → Credentials**.
* **Secret Key**: in the same keys window.

![Bucket connection data in the panel](https://3894148717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxksPMyYRDCe4qKkhbpcY%2Fuploads%2F6xK4beTqjepAkaqCOqhp%2Falmacenamiento-objetos-cliente-s3-01.png?alt=media\&token=c9af9480-e332-4afa-9bf7-2ba771eff7c5)

<figure><img src="https://3894148717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxksPMyYRDCe4qKkhbpcY%2Fuploads%2FX1o0xqywN2bblFXnr1lH%2Falmacenamiento-objetos-cliente-s3-02.png?alt=media&amp;token=2c32a764-ca91-4057-9e0d-12a75adc8a5c" alt="Pestaña Users con la ventana Credentials (Access key y Secret key)"><figcaption><p>User credentials in the Users tab</p></figcaption></figure>

> #### 🚧 Keep the Secret Key safe
>
> The Secret Key is sensitive: treat it like a password and do not share it.
>
> Together with the Access Key, it authenticates your S3 client's access to the bucket.

### Step 2. Configure the S3 client

Enter that data in your S3 client. The exact way varies by application, but they all ask for the same thing: the URL from step 1, the keys (Access Key and Secret Key) and, depending on the user, the path. Common clients are **CyberDuck** and **S3 Browser**.

![Configuration of the data in the S3 client](https://3894148717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxksPMyYRDCe4qKkhbpcY%2Fuploads%2F93gYCgEptPppbmXU4Yfr%2Falmacenamiento-objetos-cliente-s3-03.png?alt=media\&token=7c13374b-9c0a-4f14-9e2c-53f32321ecd0)

<figure><img src="https://3894148717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxksPMyYRDCe4qKkhbpcY%2Fuploads%2FQAUHkMrRArp7uyB5waC5%2Falmacenamiento-objetos-cliente-s3-04.png?alt=media&amp;token=a871f316-f752-44d8-8dd8-fb672f5b7710" alt="Cliente S3 conectado mostrando el bucket"><figcaption><p>Bucket visible in the S3 client after connecting</p></figcaption></figure>

> #### 📘 Owner (OWNER) versus the rest of the users
>
> There is a key difference depending on which user you connect with:
>
> * The **owner** (OWNER) of the bucket accesses the resource directly, without configuring anything else: the connection redirects them automatically.
> * The **other users** do not have direct access, so they must fill in the **path** with the name of the bucket they want to access.
>
> If a user who is not the owner cannot see the content, it is almost always because they forgot to specify the path.

### Conclusion

Integrating with an S3 client comes down to collecting four data items from the panel — endpoint, path, Access Key and Secret Key — and entering them in the application.

The only nuance worth remembering is the owner one: the OWNER enters directly, while the other users have to specify the bucket path.

With that, you manage your Object Storage from whichever S3 client you prefer, just like any storage compatible with the protocol.

### Next steps

* Review the service and bucket concepts in [Object Storage concepts.](https://docs.plenit.com/docs-en/productos/object-storage/concepts.md)
* Review the organization of your buckets in [Buckets and objects](https://docs.plenit.com/docs-en/productos/object-storage/concepts/buckets-and-objects.md).
* Understand how users and keys work in [S3 access: users and credentials.](https://docs.plenit.com/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 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/how-to/how-to-integrate-with-an-s3-client.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.
