> For the complete documentation index, see [llms.txt](https://docs.datasaur.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.datasaur.ai/integrations/external-object-storage.md).

# External Object Storage

Integrate your own object storage when creating projects.

This integration allows you to create projects using your preferred cloud storage provider. You will have a control over access from Datasaur to your object storage.

How Datasaur handles external files depends on the project type:

* **Document labeling and bounding box labeling:** Datasaur stores only the questions and answers. The original file data remains in your object storage.
* **Span labeling and row labeling:** The data is currently processed and copied into the Datasaur database.

## Supported cloud providers

Datasaur supports integration with the following cloud storage providers:

* [Amazon S3](/integrations/external-object-storage/aws-s3.md)
* [Google Cloud Storage](/integrations/external-object-storage/google-cloud-storage.md)
* [Azure Blob Storage](/integrations/external-object-storage/azure-blob-storage.md)
* [Google Drive](/integrations/external-object-storage/google-drive.md)

## Project creation

During the first step of project creation, you can select your preferred object storage provider, as shown below. You can then enter the file keys for the files you want to label in the project.

<figure><img src="https://448889121-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MbjY0HseEqu7LtYAt4d%2Fuploads%2Fgit-blob-a7a70c721c7afcebe9b1abd947101bb01176c984%2FPCW%20-%20Step%201%20-%20EOS.png?alt=media" alt=""><figcaption><p>Select files directly from external object storage</p></figcaption></figure>


---

# 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://docs.datasaur.ai/integrations/external-object-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.