> 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.14/onboard-cortex-xsoar/single-server-deployment/deployment-guidelines.md). # Deployment Guidelines Before you install Cortex XSOAR, review the following deployment guidelines: * [AWS EC2 Deployment Guidelines](#aws-ec2-deployment-guidelines) * [Azure Virtual Machines Deployment Guidelines](#azure-virtual-machines-deployment-guidelines) * [GCP Compute Engine Deployment Guidelines](#gcp-compute-engine-deployment-guidelines) ### AWS EC2 Deployment Guidelines AWS EC2 deployments have specific technical and sizing requirements, and a set of Cortex XSOAR best practices. After you configure and verify your AWS EC2 deployment, install the Cortex XSOAR Server. **Supported AWS EC2 Instance Types** Cortex XSOAR server installation is supported on the following Amazon EC2 instance types. | Instance Type | Instance Name | | ------------- | ------------------------------------------------------- | | M5 | m5.4xlarge | | m5.12xlarge | | | m5.24xlarge | | | M4 | m4.4xlarge | | m4.10xlarge | | | m4.16xlarge | | | C5 | c5.4xlarge | | c5.9xlarge | | | c5.18xlarge | | | C4 | c4.4xlarge | | c4.8xlarge | | | R4 | r4.4xlarge | | r4.8xlarge | | | r4.16xlarge | | | T2 | Only use this instance type for evaluation and testing. | **Supported EC2 Storage** We recommend that you use EBS-optimized instances (included in C4,M4 instance family types). {% hint style="info" %} ### Note Minimum disk space for production environment is 500 GB. {% endhint %} **Network and Security** Inbound connections: Cortex XSOAR server requires that you open HTTPS port 443 for inbound connections. Outbound connections: outbound ports depending on your integrations and specific requirements. By default, AWS opens all traffic. **Supported OS** Cortex XSOAR supports server installation on these [Linux distributions](/xsoar-6-administrator-guide/6.14/onboard-cortex-xsoar/single-server-deployment/system-requirements.md#operating-systems). **AWS Backup** You can use Amazon EBS snapshots to back up your AWS EC2 instances. Use snapshots for incremental backups, point-in-time restoration, and to view history data. ### Azure Virtual Machines Deployment Guidelines Azure Virtual Machine (VM) deployments have specific technical and sizing requirements and a set of Cortex XSOAR best practices. After you configure and verify your Azure Virtual Machine, install the Cortex XSOAR Server. **Supported Azure VM sizes** Cortex XSOAR server installation is supported on the following Azure VM sizes. | Instance Type | Instance Name | | ----------------------------------- | ------------- | | D-Series v4 - General Purpose | D16as\_v4 | | D48as\_v4 | | | D96as\_v4 | | | F-Series v2 - Compute-Optimized | F48s\_v2 | | F64s\_v2 | | | F72s\_v2 | | | H-Series - High Performance Compute | H16 | | H16m | | | H16r | | | L-Series v2 | L16s\_v2 | | L48s\_v2 | | | L80s\_v2 | | | D-Series v3 - General Purpose | D16s\_v3 | | D48s\_v3 | | | D64s\_v3 | | {% hint style="info" %} ### Note The guideline for VM selection is to start with a VM from at least the General Purpose family with a minimum of 16 vCPUs and 64 GB of memory. {% endhint %} **Supported Azure managed disk** We recommend that you use a managed disk from the Premium SSD family with a minimum IOPS of 5000+ and minimum disk space of 500 GB. **Network Security** Inbound connections: Cortex XSOAR server requires that you open HTTPS port 443 for inbound connections. Outbound connections: Outbound ports depend on your integrations and specific requirements. By default, Azure Network Security groups allow all outbound traffic. **Supported OS** Cortex XSOAR supports server installation on these [Linux distributions](/xsoar-6-administrator-guide/6.14/onboard-cortex-xsoar/single-server-deployment/system-requirements.md#operating-systems). **Azure Backup** You can use Azure Snapshots to back up your Azure VM and disks. Use snapshots for incremental backups, point-in-time restoration, and to view historical data. ### GCP Compute Engine Deployment Guidelines GCP Compute Engine deployments have specific technical and sizing requirements and a set of Cortex XSOAR best practices. After you configure and verify your GCP Compute Engine VM, install the Cortex XSOAR Server. **Supported GCP Compute Engine Instance Types** Cortex XSOAR server installation is supported on the following GCP Compute Engine VM types. | VM Type | VM Name | | ------------------------------ | --------------- | | E2 - Cost Optimized | e2-standard-16 | | e2-standard-32 | | | N2 - General Purpose | n2-standard-16 | | n2-standard-48 | | | n2-standard-80 | | | N1 - High CPU | n2d-standard-16 | | n1-standard-64 | | | n1-standard-96 | | | N2D - AMD EPYC Rome processors | n2d-standard-16 | | n2d-standard-48 | | | n2d-standard-96 | | | C2 - Compute Optimized | c2-standard-16 | | c2-standard-30 | | | c2-standard-60 | | {% hint style="info" %} ### Note The guideline for VM selection is to start with a VM from at least the General Purpose family with a minimum of 16 vCPUs and 64 GB of memory. {% endhint %} **Supported GCP Storage** We recommend that you use Balanced or SSD Persistent Disks with a minimum IOPS of 5000+ and minimum disk space of 500 GB. **Network Security** Inbound connections: The Cortex XSOAR server requires that you open HTTPS port 443 for inbound connections. Outbound connections: Outbound ports depend on your integrations and specific requirements. By default, the GCP VPC firewall opens all traffic. **Supported OS** Cortex XSOAR supports server installation on these [Linux distributions](/xsoar-6-administrator-guide/6.14/onboard-cortex-xsoar/single-server-deployment/system-requirements.md#operating-systems). **GCP Backup** You can use GCP Persistent Disk Snapshots to back up your GCP Compute Engine VM Disks. Use snapshots for incremental backups, point-in-time restoration, and to view historical data. --- # 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.14/onboard-cortex-xsoar/single-server-deployment/deployment-guidelines.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.