> 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/xsoar-6-administrator-guide/6.12/onboard-cortex-xsoar/onboarding-in-cortex-xsoar/high-availability/sizing-requirements-for-high-availability-deployments.md).

# Sizing Requirements for High Availability Deployments

**App Servers**

Cortex XSOAR recommends you have at least 2 application servers meeting the requirements listed below, as well as a load balancer and shared file system.

| Component                                                                                                                                                                                            | Dev Environment Minimum | Production Minimum                                                                                                                                                                                                                                       |
| ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| CPU                                                                                                                                                                                                  | 8 CPU cores             | 16 CPU cores                                                                                                                                                                                                                                             |
| Memory                                                                                                                                                                                               | 16 GB RAM               | 32 GB RAM                                                                                                                                                                                                                                                |
| <p>Storage</p><div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p><strong>Note</strong></p><p>The storage requirement is irrespective of the file share.</p></div> | 100 GB SSD              | <p>250 GB SSD with minimum 1k dedicated IOPS</p><div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p><strong>Note</strong></p><p>Depending on the size of your log files, consider increasing this to 500 GB.</p></div> |

**File Share Server**

Cortex XSOAR recommends your file sharing server meet the following minimum requirements.

{% hint style="info" %}

### Note

* If you are using Amazon EFS, GCP File Store, or Azure Files, verify that you are only using these systems for your file sharing and not as the database or application servers.
* The file sharing server must be in the same virtual private cloud as the application servers.
  {% endhint %}

| Component | Dev Environment Minimum | Production Minimum                        |
| --------- | ----------------------- | ----------------------------------------- |
| Storage   | 100 GB SSD              | 250 GB SSD with minimum 1k dedicated IOPS |

**Elasticsearch Database Development Configuration**

| Environment | Number of Nodes | Elastic Node Roles                                                  |
| ----------- | --------------- | ------------------------------------------------------------------- |
| Minimum     | 1               | Data node                                                           |
| Recommended | 3               | All three must be data nodes, but can also function as other roles. |

**Elasticsearch Database Production Configuration**

| Environment | Number of Nodes | Elastic Node Roles                                                   |
| ----------- | --------------- | -------------------------------------------------------------------- |
| Minimum     | 3               | All three must be data nodes, but can also function as other roles.  |
| Recommended | 6               | <ul><li>3 - Data</li><li>3 master and 3 coordinating roles</li></ul> |

**Hardware Requirements**

| Component | Dev Node Minimum | Production Node Minimum                   |
| --------- | ---------------- | ----------------------------------------- |
| CPU       | 8 CPU cores      | 16 CPU cores                              |
| Memory    | 16 GB RAM        | 32 GB RAM                                 |
| Storage   | 250 GB           | 500 GB SSD with minimum 3k dedicated IOPS |


---

# 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/xsoar-6-administrator-guide/6.12/onboard-cortex-xsoar/onboarding-in-cortex-xsoar/high-availability/sizing-requirements-for-high-availability-deployments.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.