> 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.14/onboard-cortex-xsoar/deployment-steps/step-2.-set-up-an-engine.md).

# Step 2. Set up an engine

Engines are installed on a remote machine and used mainly for the following:

* Integration instances for on-prem applications. For example, the GitLab v2 integration enables you to run commands on GitLab instances.
* To execute scripts and commands that require access to on-prem resources. For example, the Active Directory v2 integration enables you to run commands in Active Directory.
* Generic Export Indicators Service. In Cortex XSOAR, you can configure an EDL to share a list of Cortex XSOAR indicators with other products in your network, such as a firewall or SIEM. For example, your Palo Alto Networks firewall can add IP addresses and domain data from the EDL to block or allow lists.
* Load balancing enables the distribution of the command execution load.

Before installation, we recommend you review the engine requirements for hardware and operating systems. Engines can be installed on Linux machines running a variety of operating systems, including Ubuntu, RHEL, Oracle Linux, and Amazon Linux.

* [Engine requirements](/cortex-xsoar-8-on-prem/8.14/configure-cortex-xsoar/engines/engine-requirements.md)
* [Install an engine](/cortex-xsoar-8-on-prem/8.14/configure-cortex-xsoar/engines/install-an-engine.md)
* [Engine air gap installation](/cortex-xsoar-8-on-prem/8.14/configure-cortex-xsoar/engines/install-an-engine/engine-air-gap-installation.md)

To learn more about engine architecture, installation, upgrades, and configuration, see [Engines](/cortex-xsoar-8-on-prem/8.14/configure-cortex-xsoar/engines/what-is-an-engine.md).


---

# 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-on-prem/8.14/onboard-cortex-xsoar/deployment-steps/step-2.-set-up-an-engine.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.