> 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-xdr-5.x/detect-investigate-and-respond-to-threats/investigate-and-respond-to-cases/automation/engines/manage-engines.md).

# Manage engines

You can manage your engines and load-balancing groups by going to Settings → Configurations → **Data Broker** → **Engines**.

You can view engine names, hosts, status, connection, and other engine information.

You can do the following:

| Option                 | Description                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
| ---------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Load-Balancing Group   | <p>It is useful to create separate load-balancing groups. For example:</p><ul><li>Use separate load-balancing groups for different integrations and instances. Create Load-Balancing groups for certain tasks, which can help segregate the infrastructure of critical integrations.</li><li>Managed Security Service Providers may want to split internal engines and SaaS product engines.</li><li>If you have multiple AWS accounts that are not connected and do not want a single point of failure for AWS integrations that use STS.</li></ul><p>You can do the following:</p><ul><li><p>Add/remove engines to a load-balancing group</p><p>You can only add the engine to the load-balancing group after you have connected the engine.</p><p>If you want to remove the last engine from a specific load-balancing group, if one or more integration instances use that engine, you will get an error. Before moving the engine, you need to assign <strong>Run</strong> on to a different engine or no engine for each of the integration instance settings.</p></li><li><p>Create load-balancing groups</p><p>When selecting Load-Balancing Group → <strong>Add to new group</strong>, you can create multiple load-balancing groups and decide which engines are part of each group.</p><p>Users can move an engine from one group to another. A group will be deleted when the last engine is removed from it.</p><p>Each engine can only belong to one group.</p></li></ul> |
| Upgrade Engine         | Relevant for Shell installation only. If you didn't install an engine using the Shell installation, you will need to remove the engine and do a fresh installation. For more information, see [Upgrade an engine](/cortex-xdr-5.x/detect-investigate-and-respond-to-threats/investigate-and-respond-to-cases/automation/engines/upgrade-an-engine.md).                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                  |
| Get Logs               | Logs are located in **`/var/log/demisto`**. For multiple engines, logs are located in **`/var/log/demisto/`*****`<name of the engine>`***. For example, **`var/log/demisto.d1_e1`**.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    |
| Edit Configuration     | Relevant for Shell installation only. Enables you to edit the `d1.conf` file without having to access the file on your remote machine. For more information, see [Configure engines](/cortex-xdr-5.x/detect-investigate-and-respond-to-threats/investigate-and-respond-to-cases/automation/engines/configure-engines.md).                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
| Download Configuration | Download the `d1.conf` file to view the attribute values.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
| Delete Engine          | Deletes an engine from Cortex XDR. To remove the engine from your remote machine, see [Remove an engine](/cortex-xdr-5.x/detect-investigate-and-respond-to-threats/investigate-and-respond-to-cases/automation/engines/remove-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-xdr-5.x/detect-investigate-and-respond-to-threats/investigate-and-respond-to-cases/automation/engines/manage-engines.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.