> 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/quickstart.md).

# Quick Start

Setting up Object Storage takes two steps: you create the repository with its quota and assign it an owner user. 

Connecting the software via S3 comes next, using the repository credentials.

> #### 📘 What you get
>
> An Object Storage repository created, with its quota and its owner user, ready to connect via S3 or to start uploading objects from the panel.

### Before you start

* Be signed in to the Plenit platform.
* Have an organization with at least one user, or create one during setup.

### Start setup

Depending on whether you already use the service or it is your first time, you reach the wizard through one of these paths. All three end up in the same place.

| Situation                             | How you start                                                                                         |
| ------------------------------------- | ----------------------------------------------------------------------------------------------------- |
| You already use Object Storage        | Go into the service and click **New subscription**, at the top right of the list                      |
| It's your first time with the service | On the product page, click **I want to try it now**                                                   |
| From a specific client                | Go to **Organization › Subscriptions** and choose **Object Storage** in "What do you want to set up?" |

<figure><img src="/files/207d06c858d39629a6ac0cf14856049786b2fbab" alt=""><figcaption><p><em>From the service list you can see the aggregated usage and create a new repository with New subscription, at the top right.</em></p></figcaption></figure>

<figure><img src="/files/3623782ece15278a73dc0ba944574c770b602615" alt=""><figcaption><p><em>The first time, you enter the same wizard from the product page, with I want to try it now.</em></p></figcaption></figure>

### Step 1. Create the repository and set the quota

In the wizard:

1. Enter the **subscription name**, which will help you identify it.
2. Define the **storage quota** with the slider (from 100 GB). As you move it, you can see the estimated cost per month and per hour. You can increase it later if it grows.
3. Move on to the next step.

> #### 📘 The name only accepts letters and numbers
>
> Due to a service limitation, the repository identifier is made up only of letters and numbers, with no spaces, no uppercase letters, and no special characters.&#x20;
>
> Keep this in mind when naming the subscription.

<figure><img src="/files/d553aff32ae797f3f7d664fc3223652149abbe87" alt=""><figcaption><p><em>Step 1. Name the repository and set the quota with the slider (from 100 GB); you can increase it later if it grows.</em></p></figcaption></figure>

### Step 2. Assign the owner user

Select the user who will be **owner** of the repository. The owner has full permissions, and there can only be one per repository. If one does not exist, create it on the spot with **New user** and their email address. When you click **Save**, we create the repository.

> #### 📘 The rest of the users, later
>
> The other users who will access it are added after setup, with their specific permissions. You have that in [S3 access: users and credentials.](/docs-en/productos/object-storage/concepts/s3-access-users-and-credentials.md)

<figure><img src="/files/d691e6b523b3f3c1b53c676838881c63585c23f8" alt=""><figcaption><p><em>Step 2. Choose the repository owner user, or create a new one on the spot.</em></p></figcaption></figure>

### Step 3. Check and collect the connection data

The repository appears as a **card in the panel**. When you open it, you have the service tabs (Summary, Bucket, Users, Structure) and the summary with the **usage** (quota, users, objects, and uploads).&#x20;

From the **Connect** button and from the **Users** tab, you gather what you need to connect via S3: the endpoint, the repository name, and, in each user's access, the **access key** and the **secret key**.

<figure><img src="/files/41c6a7d4cfeeb712df91136950b7932c6f81c603" alt=""><figcaption><p><em>Once created, when you enter the repository you have the summary with usage and the Connect button with the S3 connection data.</em></p></figcaption></figure>

### You now have the repository created

From here, the next step is to put it to work:

* Connect the software via S3 with commands or with a client: [How to integrate with an S3 client.](/docs-en/productos/object-storage/how-to/how-to-integrate-with-an-s3-client.md)
* Give the rest of the users access and manage their keys: [S3 access: users and credentials.](/docs-en/productos/object-storage/concepts/s3-access-users-and-credentials.md)
* Enable version retention, from the **Bucket**: [tab: Versioning and immutability.](/docs-en/productos/object-storage/details/versioning-and-immutability.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/quickstart.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.