> For the complete documentation index, see [llms.txt](https://academy.shade.inc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://academy.shade.inc/shade-academy/shade-academy-fr/byos/bring-your-own-s3-storage.md).

# Apportez votre propre stockage S3

Shade vous permet de connecter un bucket S3 auto-hébergé comme backend de stockage pour Shade.

Vous pouvez connecter votre propre stockage S3 au cloud Shade, ce qui vous permet de configurer vos propres buckets, régions et autorisations pour votre équipe. Il s’agit essentiellement de payer Shade en tant que service, avec la possibilité de monter et de rechercher vos ressources sans avoir à payer pour le stockage.

{% hint style="danger" %}
Shade devra formater votre bucket pour correspondre à notre API backend. Cela signifie que vos fichiers seront découpés en blocs avec des noms UUID irréguliers et sans aucun dossier. Votre équipe ne pourra pas utiliser le bucket S3 comme un stockage de fichiers « normal » avec des dossiers. Pour plus d’informations, veuillez nous contacter [ici](https://cal.com/team/shade-inc/shade-demo).
{% endhint %}

## Configuration d’un lecteur BYOS3

<figure><img src="https://2926217644-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FUNq6h2Bfw7aAK0J2ffnZ%2Fuploads%2FeRbjfeKFykYE80HGi1Pv%2FNewBYOSStudio.gif?alt=media&amp;token=7b75bd58-20b0-4e38-8d80-cd20f5ae8010" alt=""><figcaption></figcaption></figure>

Les fichiers téléversés vers Shade via le navigateur, l’application de bureau ou le montage ShadeFS apparaîtront dans vos buckets S3 sous forme de « blobs » et de « chunks ».


---

# 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://academy.shade.inc/shade-academy/shade-academy-fr/byos/bring-your-own-s3-storage.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.
