> 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.10/configure-cortex-xsoar/incident-configuration/configure-incident-export-and-delete/configure-access-to-external-storage.md).

# Configure access to external storage

Configure external storage access for Cortex XSOAR 8.10 On-prem incident exports.

Before exporting incidents, you must have an external storage option configured. You can use an Amazon S3 bucket, any S3 compatible bucket, or NFS. Verify that your firewall allows traffic from Cortex XSOAR to your chosen storage solution, and then add your external storage to the **External Storage** settings in Cortex XSOAR.

{% hint style="info" %}

### Note

If you are only deleting incidents, without exporting, no external storage or firewall configuration is required.

If you are using Amazon S3, you will need the bucket name, region, access key, and secret key. In addition, the following Amazon S3 bucket policies must be allowed:

* s3:PutObject
* s3:GetObject
* s3:DeleteObject
* s3:ListBucket

If you are using an S3 compatible bucket, you will need the bucket name, URL, access key, and secret key.

[Example: Retrieve information from Amazon S3](/cortex-xsoar-8-on-prem/8.10/configure-cortex-xsoar/incident-configuration/amazon-s3-configuration-example.md)
{% endhint %}

### **Configure external storage in the Cortex XSOAR 8 On-prem tenant**

1. Go to **Settings & Info** → **Settings** → **System** → **External Storage** → **New**.
2. Enter a storage name of your choice and select whether the storage is **NFS**, **AWS S3** or **S3-Compatible**.
   * If you are using NFS, enter the server IP address and the full path to the storage directory. Enter a username and password if required to access the NFS.
   * If you are using Amazon S3, enter the **Bucket name**, **Region**, **Access key**, and **Secret key**.
   * If you are using an S3-compatible storage option, enter the **Bucket name**, **URL**, **Access key**, and **Secret key**.
3. **Test connection**.

   If the connection fails, confirm that your firewall permits traffic from Cortex XSOAR to your storage solution, that the credentials are correct, and that you have write permissions to the bucket.
4. **Save** the configuration.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://cortex-docs.paloaltonetworks.com/cortex-xsoar-8-on-prem/8.10/configure-cortex-xsoar/incident-configuration/configure-incident-export-and-delete/configure-access-to-external-storage.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.