> 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

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

That allows you to 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 for the service.
* Have an **Object Storage**subscription. If you don't have one yet, set it up with the [Object Storage Quick Start.](/docs-en/productos/object-storage/quickstart.md)
* Having an S3 client installed (for example, CyberDuck or S3 Browser) on your computer.

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

In [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)**: `s3.plenit.com`.
* **Path (bucket name)**: in the **Bucket**tab, field **My bucket**.
* **Access Key**: in **Users → user → menu (…) → Keys**.
* **Secret Key**: in the same keys window.

{/\* 📸 SCREENSHOT 1 · Summary/Bucket (name and endpoint) and Users › Keys (Access/Secret) \*/}

![Bucket connection data in the panel](https://REEMPLAZA-URL/almacenamiento-objetos-cliente-s3-01.png)

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

### Step 2. Configure the S3 client

Enter that data into your S3 client. The exact way varies depending on the application, but they all ask for the same thing: the endpoint (`s3.plenit.com`), the keys (Access Key and Secret Key) and, depending on the user, the path. Common clients are **CyberDuck** and **S3 Browser**.

{/\* 📸 SCREENSHOT 2 · example of configuration in an S3 client (endpoint, keys, path) \*/}

![Configuration of the data in the S3 client](https://REEMPLAZA-URL/almacenamiento-objetos-cliente-s3-02.png)

> #### 📘 Owner (OWNER) vs. 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 automatically.
> * The **rest of the users** do not have direct access, so they must fill in the **path** field with the name of the bucket they want to access.
>
> If a user who is not the owner does not see the content, it is almost always because they forgot to specify the path.

### Conclusion

Integrating with an S3 client comes down to gathering four pieces of data from the panel — endpoint, path, Access Key, and Secret Key — and entering them into the application.

The only nuance worth remembering is the owner’s: 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.](/docs-en/productos/object-storage/concepts.md)
* Review the organization of your buckets in [Structure and buckets.](/docs-en/productos/file-storage/concepts/folder-structure.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/how-to/how-to-integrate-with-an-s3-client.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.