---
title: "Connect to a repository with the MinIO CLI or s3cmd"
description: "Set up the MinIO CLI or s3cmd for a Model Repository with the ready-made commands on the Using CLI tab, and copy a model folder in and out."
content_type: "how-to"
product: "model-repository"
platform: "TIR"
url: "/tir/model-repository/how-to/connect-to-a-repository-with-an-s3-tool/"
topic: ["create-and-connect"]
---

# Connect to a repository with the MinIO CLI or s3cmd

Connect the MinIO CLI (`mc`) or `s3cmd` to a repository from your own computer or from an instance. The repository's files are in an E2E Object Storage bucket, so any S3-compatible CLI or SDK works. The portal recommends the MinIO CLI.

## Before you begin

- A repository; see [Create a repository](/tir/model-repository/how-to/create-a-repository/).
- Permission to read model repositories in the project. A Member gets it through a policy that allows reading for the Inference service. Reading lets you open the **Using CLI** tab.

## Open the Using CLI tab

In TIR, open your project. In the side menu, under **Inference**, select **Model Repository**, then select the row of the repository and open the **Using CLI** tab. It has two panels, **Setup Minio CLI** and **Setup s3cmd**. Each panel has ready-to-paste text with this repository's endpoint and keys filled in, and a link to a guide for the tool. The secret key is written out in full, so keep what you copy to yourself.

## Set up the MinIO CLI

**Setup Minio CLI** has tabs for **Linux**, **macOS**, and **Using Windows**. It lists, in order:

1. **Install mc**. On Linux, it downloads `mc` and adds it to your path. On macOS, it uses `brew install minio/stable/mc`. On Windows, it downloads `mc.exe` from the MinIO site.
2. **Check mc version**, which runs `mc --version`.
3. **Update mc**, which runs `mc update`.
4. **Setup Host**, which saves the repository's endpoint and keys under a name. The portal uses the repository's name.
5. **Upload files to Model Repository**, **List files in Model Repository**, and **Download files from Model Repository**.

The commands have this shape. Replace each placeholder with the value the portal prints.

- `<repository-name>` is the name `mc` saves on your computer for this endpoint and key pair. You can choose any name; it is stored only on your computer.
- `<bucket-name>` is the repository's **Bucket Name** from the **Overview** tab.
- `<local-folder>` is a folder on your computer.

```bash
mc alias set <repository-name> <EOS endpoint> <access key> <secret key>
mc cp -r <local-folder> <repository-name>/<bucket-name>
mc ls <repository-name>/<bucket-name>/
mc cp -r <repository-name>/<bucket-name> <local-folder>
```

The first command connects, the second uploads a folder, the third lists the files, and the fourth downloads them. For an `mc` release older than RELEASE.2025-05-21T01-59-54Z, use `mc config host add` in place of `mc alias set`. The **macOS** tab shows this note.

```bash
mc config host add <repository-name> <EOS endpoint> <access key> <secret key>
```

## Set up s3cmd

**Setup s3cmd** gives three blocks to put in your `s3cmd` settings file. The first sets the host and bucket host to the **EOS Endpoint** and turns HTTPS on. The second holds your keys. The third turns off the older signature, so `s3cmd` uses the S3 v4 signature.

```text
host_base = <EOS endpoint>
host_bucket = <EOS endpoint>
use_https = True
access_key = <access key>
secret_key = <secret key>
signature_v2 = False
```

## Check the connection

Copy a folder in, then open the **Model Files** tab and refresh the page to see the files. You can also list the repository with your tool to confirm the upload finished.

Your tool is now connected. For folder layouts, versions, and the SDK, see [Upload model files](/tir/model-repository/how-to/upload-model-files/). For help with a message, see [Troubleshooting Model Repository](/tir/model-repository/troubleshooting/model-repository/).