# File Storage Overview

- Published on Sep 17, 2024

## File storage

As described in [Infrastructure Requirements (Production)](https://help.hyperscience.ai/deployment/docs/infrastructure-requirements#h_01H93A0FQN3HEZP26MTJ67N2GP), a file storage location will need to be provided. The instructions for configuring the different options can be found in the articles below:

- [S3 Cloud Storage](https://help.hyperscience.ai/deployment/docs/s3-cloud-storage)
- [Azure Blob Storage](https://help.hyperscience.ai/deployment/docs/azure-blob-storage)
- [Google Cloud Storage](https://help.hyperscience.ai/deployment/docs/google-cloud-storage)
- [Network-attached Storage or Local Storage](https://help.hyperscience.ai/deployment/docs/network-attached-storage-or-local-storage)

### _HS_PATH/media_ verification

By default in v35.0.24+ and v37 and later, _run.sh init_ verifies the presence and ownership of _HS_PATH/media_. If _HS_PATH/media_ does not exist or is not owned by _uid 1000_ and _gid 1000_, the file store will not be initialized, and the application initialization will fail.

If you need to bypass this verification (e.g., for debugging purposes), you can add _HS_RUN_ON_BROKEN_MEDIA_DIR=true_ to your ".env" file. Do not add this variable unless instructed to do so by Hyperscience.