> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/cortex-xsoar-8-on-prem/8.13/back-up-and-restore-cortex-xsoar/set-up-access-to-an-external-storage.md).
# Set up access to an external storage
Cortex XSOAR supports the following external storages:
* AWS S3 buckets.
* S3 compatible buckets, such as MinIO
* NFS
How to set up access to external storage from Cortex XSOAR
1. Configure the following for the relevant storage type.
| Storage Type | Prerequisites |
| ------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| AWS S3 | An S3 named bucket ready for use with read and write permissions, with known access and a secret key.
Example: AWS S3 configuration example
|
| S3-Compatible | An S3-compatible bucket (such as MinIO) ready for use with read and write permissions, and an (http or https) URL.
Note
Custom CA certificates (such as self-signed certificates) are automatically propagated by the installer. For more information, see Manage custom certificates.
- An installed NFSv4.1 server (with a static IP address).
- A dedicated disk on the NFS server with the minimum disk space required to store backups. For more information, see Hardware requirements.
- Access to the NFS server from the Cortex XSOAR cluster via ports 2049 and 111.
Authentication for the NFS server:
Authentication methods vary depending on the customer, and password authentication is currently not supported. The officially supported set of permissions under the /etc/exports file on the NFS server includes allowing an IP address to access a specific path with specified permissions as follows:
/path/to/nfsshare \(rw,sync,no\_root\_squash,no\_subtree\_check)
The set of NFS options and user permissions should allow any client user to connect to the NFS mount point. It is possible to use user mapping as long as it allows read-write permissions to any user from the client. Execution is recommended to be disallowed. Chroot is recommended and supported.
A dedicated partition or disk for the NFS mount point.
The mount point should be on a dedicated partition or disk in order to separate any critical file system from the NFS operation. It is also recommended to use only one mount point per partition or disk.
|
2. Navigate to Settings & Info → **Settings** → **System** → **External Storage**.
You can create, view, or delete external storages. For each one, you can create and view the connection details, as well as attach a name for future reference.
3. Click **New**.
4. Define the following for the relevant storage type.
| Storage Type | Storage Details |
| ------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| AWS S3 | - Bucket name: the name of the bucket where backups will be stored.
- Region: The AWS region where the S3 bucket is located.
- Access key: The access key associated with the AWS account for authentication.
- Secret key: The secret key corresponding to the access key for secure access.
|
| S3-Compatible | - Bucket name: the name of the bucket where backups will be stored.
- URL: the URL of the S3-Compatible storage solution for access.
- Access key: the access key for authentication to the S3-Compatible storage.
- Secret key: The secret key associated with the access key for secure access.
|
| NFS | - Address: The IP address or hostname of the NFS server.
- Path: The path to the NFS server where the backups will be stored.
|
5. Click **Test connection**.
6. Click **Save**.
The new external storage is added to the **External Storage** page.
---
# 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://cortex-docs.paloaltonetworks.com/cortex-xsoar-8-on-prem/8.13/back-up-and-restore-cortex-xsoar/set-up-access-to-an-external-storage.md?ask=&goal=
```
`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.