> 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.14/onboard-cortex-xsoar/high-availability/deploy-engines-in-a-high-availability-environment.md).

# Deploy Engines in a High Availability Environment

Deploy Cortex XSOAR 6.14 engines in high availability and route engine connections through a load balancer.

Engines deployed prior to the migration to Elasticsearch will remain connected to the newly migrated Cortex XSOAR application server.

When additional Cortex XSOAR application servers are deployed, and placed behind a load balancer, you need to update the engines to connect through the load balancer.

1. Verify that the **`BaseURL`** and **`ExternalHostname`** server configurations have been updated on the servers to reference the load balancer url.
2. Stop the engine service.
3. Create a backup of the **`/usr/local/demisto/d1.conf`** file.
4. [Edit](/xsoar-6-administrator-guide/6.14/onboard-cortex-xsoar/engines/configure-engines.md#UUID-0bab90bb-978d-3430-649d-1cbcb8b560d3) the **`/usr/local/demisto/d1.conf file`** on the engine.
5. Set the first line in the `EngineURLs` section to point to the new load balancer URL.

   ```programlisting
   {
       "LogLevel": "info",
       "LogFile": "d1.log",
       "EngineURLs": [
           "wss://LOADBALANCERURL/d1ws"
       ],
       …
   }
   ```
6. Start the engine service.
7. Validate the engine is connected by going to Settings → **Engines**.


---

# 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/xsoar-6-administrator-guide/6.14/onboard-cortex-xsoar/high-availability/deploy-engines-in-a-high-availability-environment.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.