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

# Shared Storage

IDEA supports multiple type of storage backend such as:

* Elastic Block Storage (<https://aws.amazon.com/ebs/>)
* Elastic File System (<https://aws.amazon.com/efs/>)
* FSx for Lustre (<https://aws.amazon.com/fsx/lustre/>)
* FSx for OpenZFS (<https://aws.amazon.com/fsx/openzfs/>)
* FSx for NetApp OnTap (<https://aws.amazon.com/fsx/netapp-ontap/>)
* FSx for Windows File Server (<https://aws.amazon.com/fsx/windows/>)

You can choose to deploy your file-system partition logic via the "Shared Storage" module on IDEA. You can let IDEA creates the storage backend (when possible) or use existing storage solutions running on your AWS account.

Additionally[, you can map your mount point based on IDEA Project membership](/modules/cluster-manager/projects-management.md) such as:

* Mount `/team1/project_name` (FSx for Lustre) for all Linux [Virtual Desktop Interfaces](/modules/virtual-desktop-interfaces.md) launched for Project A
* Mount `\\windows\project_name` (FSx for Windows File Server)for all Windows [Virtual Desktop Interfaces](/modules/virtual-desktop-interfaces.md)
* Mount `/team2/shared` Elastic File System for all [Virtual Desktop Interfaces](/modules/virtual-desktop-interfaces.md) launched by team B
* Mount `/fsx-scratch` FSx for OpenZFS for all compute nodes provisioned to run [HPC Workloads](/modules/hpc-workloads.md) on `queue1` or `queue2`

Refer to [Storage Management](/modules/storage/storage-management.md) to learn more about the integration of Shared Storage module onto the IDEA ecosystem


---

# 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.idea-hpc.com/modules/storage.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.