> 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-saas/configure-cortex-xsoar/incident-configuration/export-cortex-xsoar-incidents-to-cloud-storage.md).

# Export Cortex XSOAR incidents to cloud storage

Export Cortex XSOAR 8 SaaS incidents as JSON files to Amazon S3, S3-compatible storage, or Azure Blob Storage.

Export Cortex XSOAR 8 SaaS incidents to external cloud storage. Exports support Amazon S3, S3-compatible storage, and Azure Blob Storage.

### Exported incident data

Incidents are exported as JSON files containing:

* Incident data, including all incident fields
* Context data
* Investigation data
* War Room entries

You can also export incident attachments.

### Configure cloud storage exports

Before exporting, configure egress to your storage solution in Cortex Gateway. Then configure **External Storage** settings in Cortex XSOAR.

You can schedule incident exports or export incidents on demand.

* [Configure access to external storage](/cortex-xsoar-8-saas/configure-cortex-xsoar/incident-configuration/export-cortex-xsoar-incidents-to-cloud-storage/configure-access-to-external-storage.md)
* [Schedule incident export](/cortex-xsoar-8-saas/configure-cortex-xsoar/incident-configuration/export-cortex-xsoar-incidents-to-cloud-storage/schedule-incident-export.md)
* [Export incidents on demand](/cortex-xsoar-8-saas/investigate-and-respond-to-threats/incidents-and-indicators-investigation/incident-management/export-incidents/export-incidents-on-demand.md)
* [Amazon S3 configuration example](/cortex-xsoar-8-saas/configure-cortex-xsoar/incident-configuration/export-cortex-xsoar-incidents-to-cloud-storage/amazon-s3-configuration-example.md)

{% hint style="info" %}

* The Azure Blob Storage option is disabled by default; contact Customer Support if you would like to enable.
* The first time incidents are exported, the process may take multiple days or weeks, depending on the number of incidents and the amount of data. The previous export must be completed before the system begins another export.
* Once an incident has been exported, it is not exported again, even if it remains in the system and is modified after the export.
* Exported incidents cannot be imported back into Cortex XSOAR.
* Retained incidents are not exported.
  {% endhint %}


---

# 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-saas/configure-cortex-xsoar/incident-configuration/export-cortex-xsoar-incidents-to-cloud-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.