> For the complete documentation index, see [llms.txt](https://docs.kyso.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kyso.io/posting-to-kyso/importing-files-from-s3.md).

# Importing Files from S3

{% hint style="danger" %}
**Note that this feature is available upon request only.**
{% endhint %}

Our team has built a mass import option for pulling 00s, if not 000s of existing files currently stored in s3 buckets. See the gif below for a beta view of how it works on the UI:

You simply need your AWS key and path to the folder(s) on S3 and can create your own metadata mappings so all files are automatically categorised into Kyso Organizations and Channels on import.  You can set default values for any file with missing metadata. And the files are immediately indexed full-text for search.

This workflow can work for a 1-time import OR a continuous integration, in which Kyso pulls in edited files in an s3 folder on a periodic basis or when executed.

{% hint style="info" %}
This workflow can also just be run from the Command Line with the Kyso CLI if preferred to the UI option above.
{% endhint %}


---

# 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.kyso.io/posting-to-kyso/importing-files-from-s3.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.