> 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-agentix/onboard-cortex-agentix/post-deployment-steps/set-up-an-engine.md).

# Set up an engine

Set up a Cortex AgentiX engine on a remote machine.

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.
* 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 Indicator export service. In Cortex AgentiX, you can configure an EDL to share a list of Cortex AgentiX indicators with other products on 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.

{% stepper %}
{% step %}
Select **Settings** → **Configurations** → **Data Broker** → **Engines** → **Create New Engine**.
{% endstep %}

{% step %}
In the Engine Name field, add a meaningful name for the engine.
{% endstep %}

{% step %}
Select one of the installer types from the list.
{% endstep %}

{% step %}
(Optional) (Shell only) Select the checkbox to enable multiple engines to run on the same machine.

If you have an existing engine and you did not select the checkbox, and now you want to install another engine on the same machine, you need to delete the existing engine.
{% endstep %}

{% step %}
(Optional) Add any required configuration in JSON format.
{% endstep %}

{% step %}
Click OK to create the engine.
{% endstep %}
{% endstepper %}

To learn more about engines, requirements, and installation, see [Install an engine](/cortex-agentix/configure-cortex-agentix/engines/install-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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://cortex-docs.paloaltonetworks.com/cortex-agentix/onboard-cortex-agentix/post-deployment-steps/set-up-an-engine.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.