> For the complete documentation index, see [llms.txt](https://docs.pentaho.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pentaho.com/pdia-data-integration/10.2-data-integration/pdi-transformation-steps-reference-overview/elasticsearch-rest-bulk-insert/options-elasticsearch-rest-bulk-insert/general-tab-elasticsearch-rest-bulk-insert.md).
# General tab
Use the **General** tab set connections for the Elastic nodes and set options for the destination index.
Specify the **Connection** options for each server in the table of the **Servers** tab. The following table describes these connection options:
| Column | Description |
| ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **#** | Number of the field’s entry. |
| **Address** | Enter the hostname (optionally specified with a variable) of the node you want to connect to. |
| **Port** | Enter the port (optionally specified with a variable) of the Elastic REST interface. |
| **Scheme** | Enter the scheme or protocol (optionally specified with a variable) to use when performing REST communication, which is usually http, or https for secured Elastic nodes. |
Set user verification options the **Authentication** tab to choose and test a verification method for the Elastic node user. The following table describes these user verification options:
| Field | Description |
| ------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Authentication** | Select the authentication method for the Elastic nodes:
Specify this method if you do not want to authenticate when connecting.
Specify the Username and Password to use basic authentication when connecting to the Elastic nodes.
|
| **Test** | Click to test the connection and authentication settings. |
Use the \*\*Index\*\* options to name and test the output Elastic index.
| Field | Description |
| ---------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Index** | Specify the name of the target index for the documents submitted by bulk insert requests. This value can be specified as a variable. If an index with that name does not yet exist in Elasticsearch, it creates one. |
| **Test** | Click to test the connectivity to the desired output index. |
| **Create** | Click to create the index if it does not exist. |
---
# 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://docs.pentaho.com/pdia-data-integration/10.2-data-integration/pdi-transformation-steps-reference-overview/elasticsearch-rest-bulk-insert/options-elasticsearch-rest-bulk-insert/general-tab-elasticsearch-rest-bulk-insert.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.