> 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-xpanse/active-response/engines/manage-engines.md).

# Manage Engines

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

You can view engine names, hosts, status, connection, etc.

You can do the following:

* Add/remove engines to the [Load-Balancing Group](/xsoar-6-administrator-guide/6.14/onboard-cortex-xsoar/engines/cortex-xsoar-engines-overview.md#engine-load-balancing).

  You can only add the engine to the Load-Balancing group after you have connected the engine.
* Create Load-Balancing Groups

  When selecting Load-Balancing Group → **Add to new group**, you can create multiple Load-Balancing groups and decide which engines are part of each group. It is useful to create separate Load-Balancing groups. For example,

  * 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.
  * Managed Security Service Providers may want to split internal engines and SaaS product engines.
  * 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.

  Users can move an engine from one group to another. A group will be deleted when the last engine is removed from it.

  Each engine can only be part of a separate group.
* Get engine 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`**.
* Upgrade an engine

  If an engine requires an upgrade, the **Status** column shows those engines that require upgrades. Select the checkbox for the engine that requires an upgrade and click **Upgrade Engine**. When the upgrade finishes, the version appears in the **Cortex XSIAM Version**. The upgrade procedure can take several minutes.

  You can only upgrade the engine if you installed the engine with the shell installer. To upgrade engines that were not installed with the shell installer, you need to remove the engine and do a fresh install. For more information, see [Install an Engine](/cortex-xpanse/active-response/engines/engine-installation.md). For troubleshooting engines, see [Troubleshoot Engines](/cortex-xpanse/active-response/engines/troubleshoot-engines.md).
* Delete an engine


---

# 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-xpanse/active-response/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.