> 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/single-server-deployment/deployment-guidelines/gcp-compute-engine-deployment-guidelines.md).

# 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.12/onboard-cortex-xsoar/onboarding-in-cortex-xsoar/single-server-deployment/system-requirements.md).

**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.12/onboard-cortex-xsoar/onboarding-in-cortex-xsoar/single-server-deployment/deployment-guidelines/gcp-compute-engine-deployment-guidelines.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.