`**
Use the following flags:
| Flag | Type | Description |
| -------------------------- | ------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `-elasticsearch-url` | String | Elasticsearch URL addresses (comma-separated). For example, `http://test1:9200,http://test2:9200` |
| `-elasticsearch-api-key` | String | The Elasticsearch API key, which should be used in licensed versions.
Note: If you use this flag, you do not need to use the -elasticsearch-username and -elasticsearch-password flags.
|
| `-elasticsearch-username` | String | The Elasticsearch username. This flag is used with the -elasticsearch-password flag.
Note: If you use this flag, you do not need to use the -elasticsearch-api-key flag.
|
| `-elasticsearch-password` | String | The Elasticsearch password. This flag is used with the -elasticsearch-username flag.
Note: If you use this flag, you do not need to use the -elasticsearch-api-key flag.
|
| `-elasticsearch-proxy=` | Boolean | Whether to use a proxy when communicating with Elasticsearch. Can be **`true`** or **`false`**. Default is **`false`**. |
| `-elasticsearch-insecure=` | Boolean | Whether to trust any certificate when communicating with Elasticsearch. Can be **`true`** or **`false`**. Default is **`false`**. |
| `-elasticsearch-timeout` | Integer | The amount of time (in seconds) before Elasticsearch times out. Default is 20 seconds. |
2. Accept the EULA and add the information when prompted.
3. The Server HTTPS port (default is 443)
4. Enter the [Elasticsearch](/cortex-xsoar-6-installation-guides/6.14/cortex-xsoar-installation-guide/single-server-installation/install-cortex-xsoar-with-elasticsearch.md) details, such as the URL, timeout, etc.
5. Type the name of the Admin user (default is admin).
6. Type the password (default is admin).
{% endstep %}
{% step %}
### Verify the installation
( Optional) After the installation has completed, do the following:
1. Confirm that the Cortex XSOAR server status is active, by running the **`systemctl status demisto`** command.
If the server is not active, run the **`systemctl start demisto`** command to start the server.
2. Confirm that the Docker service status is active, by running the **`systemctl status docker`** command.
3. In a web browser, go to the **`https://`*****`serverURL`*****`:`*****`port`*** to verify that Cortex XSOAR was successfully installed.
When you open Cortex XSOAR for the first time, you need to add the license.
{% endstep %}
{% step %}
### Add the license
After the installation is complete, activate the license.
1. Log in to the Cortex XSOAR server.
2. Upload the **license** file that you downloaded from the Cortex Gateway in Step 1.
{% endstep %}
{% endstepper %}
---
# 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-xsoar-6-installation-guides/6.14/cortex-xsoar-installation-guide/single-server-installation/install-cortex-xsoar-with-elasticsearch/elasticsearch-installation.md?ask=&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.