> For the complete documentation index, see [llms.txt](https://documentation.alluxio.io/ee-ai-en/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.alluxio.io/ee-ai-en/ai-3.2/ufs/storage-overview.md).

# Storage Integrations Overview

This guide will cover general prerequisites and running Alluxio locally with your desired under storage system. To learn how to configure Alluxio with each individual storage system, please look at their respective pages. Refer to [configuring mount points](/ee-ai-en/ai-3.2/feature/alluxio-namespace-and-under-file-system-namespaces.md#configuring-for-ufs) to learn about the commands to mount the storages into Alluxio's namespace.

## Prerequisites

In preparation for using your chosen storage system with Alluxio, please be sure you have all the required location, credentials, and additional properties before you begin configuring Alluxio to your under storage system.

For the purposes of this guide, the following are placeholders.

| Storage System                                                            | Location                      | Credentials                                                                | Additional Properties                                          |
| ------------------------------------------------------------------------- | ----------------------------- | -------------------------------------------------------------------------- | -------------------------------------------------------------- |
| [Amazon AWS S3](/ee-ai-en/ai-3.2/ufs/s3.md)                               | `S3_BUCKET`, `S3_DIRECTORY`   | `S3_ACCESS_KEY_ID`, `S3_SECRET_KEY`                                        |                                                                |
| [HDFS](/ee-ai-en/ai-3.2/ufs/hdfs.md)                                      | `HDFS_NAMENODE`, `HDFS_PORT`  |                                                                            | <p>Specify Hadoop version:<br><code>HADOOP\_VERSION</code></p> |
| [Aliyun Object Storage Service (OSS)](/ee-ai-en/ai-3.2/ufs/aliyun-oss.md) | `OSS_BUCKET`, `OSS_DIRECTORY` | `OSS_ACCESS_KEY_ID`, `OSS_ACCESS_KEY_SECRET`, `OSS_ENDPOINT`               |                                                                |
| [COS](/ee-ai-en/ai-3.2/ufs/cos.md)                                        | `COS_BUCKET`, `COS_DIRECTORY` | `COS_ACCESS_KEY_ID`, `COS_ACCESS_KEY_SECRET`, `COS_REGION`, `COS_APP_ID`   |                                                                |
| [TOS](/ee-ai-en/ai-3.2/ufs/tos.md)                                        | `TOS_BUCKET`, `TOS_DIRECTORY` | `TOS_ACCESS_KEY_ID`, `TOS_ACCESS_KEY_SECRET`, `TOS_REGION`, `TOS_ENDPOINT` |                                                                |


---

# 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://documentation.alluxio.io/ee-ai-en/ai-3.2/ufs/storage-overview.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.