> 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/byos/bring-your-own-s3-storage.md).

# Bring Your Own S3 Storage

Shade allows you to connect a self-hosted S3 bucket as your storage backend for Shade.

You can connect your own S3 storage to the Shade cloud, allowing you to configure your own buckets, regions, and permissions for your team. This is essentially paying for Shade as a service, with the ability to mount and search your assets without needing to pay for storage.

{% hint style="danger" %}
Shade will need to format your bucket to match our backend API. This means your files will be chunked with irregular UUID names and without any folders. Your team will not be able to use the S3 bucket as "regular" file storage with folders. For more information, please contact us [here](https://cal.com/team/shade-inc/shade-demo).
{% endhint %}

## Setting up a BYOS3 Drive

<figure><img src="https://450378260-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>

Files uploaded to Shade either through the browser, desktop app, or ShadeFS mount will appear in your S3 buckets as "blobs" and "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/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.
