# Elasticsearch

**Elasticsearch** is a distributed, RESTful search and analytics engine used to store, index, and analyze large volumes of data in real time. By integrating Elasticsearch with Apono, you can enable temporary access to Elasticsearch for developers, data engineers, and operations teams without compromising security.

This integration allows Apono to manage just-in-time access to your Elasticsearch indices by authenticating through a connector user with scoped privileges.

***

### Prerequisites

<table><thead><tr><th width="211">Item</th><th>Description</th></tr></thead><tbody><tr><td><strong>Elasticsearch role</strong></td><td><p><a href="https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-security-put-role">Create a role</a> for the Apono connector with the following privileges.</p><pre><code>{
  "cluster": [ "monitor", "manage_security" ],
  "indices": [
    {
      "names": [ "*" ],
      "privileges": [ "monitor" ]
    }
  ]
}
</code></pre></td></tr><tr><td><strong>Elasticsearch user</strong></td><td><a href="https://www.elastic.co/docs/api/doc/elasticsearch/operation/operation-security-put-user">Create a user</a> for the Apono connector and assign the role above</td></tr><tr><td><strong>Elasticsearch endpoint</strong></td><td><p>Unique URL for your Elasticsearch deployment<br></p><p>Learn how to <a href="https://www.elastic.co/docs/deploy-manage/deploy/cloud-on-k8s/accessing-services#k8s-request-elasticsearch-endpoint">access the Elasticsearch endpoint</a>.</p><p><br><strong>NOTE</strong>: For Elastic Cloud users, the endpoint can be found in the <strong>Deployments</strong> tab of your Elastic Cloud console.</p></td></tr><tr><td><strong>Apono connector</strong></td><td><p>On-prem connection serving as a bridge between a MySQL instance and Apono:</p><ul><li><a href="../../aws-environment/apono-connector-for-aws">AWS</a></li><li><a href="../../azure-environment/apono-connector-for-azure">Azure</a></li><li><a href="../../gcp-environment/apono-connector-for-gcp">GCP</a></li><li><a href="../../kubernetes-environment/apono-connector-for-kubernetes">Kubernetes</a><br></li></ul><p>Learn how to update an existing <a href="../../aws-environment/apono-connector-for-aws/updating-a-connector-in-aws">AWS</a>, <a href="../../azure-environment/apono-connector-for-azure/updating-a-connector-in-azure">Azure</a>, <a href="../../gcp-environment/apono-connector-for-gcp/updating-a-connector-in-google-cloud">GCP</a>, or <a href="../../kubernetes-environment/apono-connector-for-kubernetes/updating-a-kubernetes-connector">Kubernetes</a> connector.</p></td></tr><tr><td>Apono HTTP proxy</td><td><a href="../network-management/installing-the-apono-http-proxy">Authorization controls</a> to manage Elasticsearch<br><br>The default Elasticsearch capabilities do not include authorization controls and therefore neither does the API. When integrating with Apono using the HTTP Proxy, you will be able to manage access to Elasticsearch using Apono Access Flows.</td></tr></tbody></table>

***

### Integrate Elasticsearch

<figure><img src="https://1094436629-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fv6MBfUGvblSdAz31yJXm%2Fuploads%2Fgit-blob-ad30d9cddd80d187e31d848c9ee4c903a4006020%2F2025-07-28_14-08-34.png?alt=media" alt="" width="375"><figcaption><p><em>Elasticsearch resource tile</em></p></figcaption></figure>

{% hint style="success" %}
You can also use the steps below to integrate with Apono using Terraform.

In step **11**, instead of clicking **Confirm**, follow the **Are you integrating with Apono using Terraform?** guidance.
{% endhint %}

Follow these steps to complete the integration:

1. On the [**Catalog**](https://app.apono.io/catalog?search=elasticsearch) tab, click **Elasticsearch**. The **Connect integration** page appears.
2. Under **Discovery**, select one or more resources to connect to Apono.
3. Click **Next**. The **Apono connector** section expands.
4. From the dropdown menu, select a connector. Choosing a connector links Apono to all the services available on the account where the connector is located.

{% hint style="success" %}
If the desired connector is not listed, click **+ Add new connector** and follow the instructions for creating a connector ([AWS](https://docs.apono.io/docs/aws-environment/apono-connector-for-aws), [Azure](https://docs.apono.io/docs/azure-environment/apono-connector-for-azure), [GCP](https://docs.apono.io/docs/gcp-environment/apono-connector-for-gcp), [Kubernetes](https://docs.apono.io/docs/kubernetes-environment/apono-connector-for-kubernetes)).
{% endhint %}

5. Click **Next**. The **Integration Config** section expands.
6. Define the **Integration Config** settings.

   <table><thead><tr><th width="218">Setting</th><th>Description</th></tr></thead><tbody><tr><td><strong>Integration Name</strong></td><td>Unique, alphanumeric, user-friendly name used to identify this integration when constructing an access flow</td></tr><tr><td><strong>URL</strong></td><td>Unique URL for your Elasticsearch deployment</td></tr></tbody></table>
7. Click **Next**. The **Secret Store** section expands.
8. [Associate the secret or credentials](https://docs.apono.io/docs/connectors-and-secrets/apono-integration-secret).

{% hint style="info" %}
If you select the **Apono** secret manager, enter the value of the username and password for the `apono-connector` user.
{% endhint %}

9. Click **Next**. The **Get more with Apono** section expands.
10. Define the **Get more with Apono** settings.

    <table><thead><tr><th width="220">Setting</th><th>Description</th></tr></thead><tbody><tr><td><strong>Credential Rotation</strong></td><td><p>(Optional) Number of days after which the database credentials must be rotated</p><p>Learn more about the <a href="../../architecture-and-security/credentials-rotation-policy">Credentials Rotation Policy</a>.</p></td></tr><tr><td><strong>User cleanup after access is revoked (in days)</strong></td><td><p>(Optional) Defines the number of days after access has been revoked that the user should be deleted</p><p><br>Learn more about <a href="../../architecture-and-security/periodic-user-cleanup-and-deletion">Periodic User Cleanup &#x26; Deletion</a>.</p></td></tr><tr><td><strong>Custom Access Details</strong></td><td>(Optional) Instructions explaining how to access this integration's resources<br><br>Upon accessing an integration, a message with these instructions will be displayed to end users in the User Portal. The message may include up to <strong>400 characters</strong>.<br><br>To view the message as it appears to end users, click <strong>Preview</strong>.</td></tr><tr><td><strong>Integration Owner</strong></td><td><p>(Optional) Fallback approver if no <a href="../../access-flows/dynamic-access-management/resource-and-integration-owners">resource owner</a> is found<br><br>Follow these steps to define one or several integration owners:</p><ol><li>From the <strong>Attribute</strong> dropdown menu, select <strong>User</strong> or <strong>Group</strong> under the relevant identity provider (IdP) platform.</li><li>From the <strong>Value</strong> dropdown menu, select one or multiple users or groups.</li></ol><p><br><strong>NOTE</strong>: When <strong>Resource Owner</strong> is defined, an <strong>Integration Owner</strong> must be defined.</p></td></tr><tr><td><strong>Resource Owner</strong></td><td><p>(Optional) Group or role responsible for managing access approvals or rejections for the resource<br><br>Follow these steps to define one or several <a href="../../access-flows/dynamic-access-management/resource-and-integration-owners">resource owners</a>:</p><ol><li>Enter a <strong>Key name</strong>. This value is the name of the tag created in your cloud environment.</li><li>From the <strong>Attribute</strong> dropdown menu, select an attribute under the IdP platform to which the key name is associated.<br><br>Apono will use the value associated with the key (tag) to identify the resource owner. When you update the membership of the group or role in your IdP platform, this change is also reflected in Apono.</li></ol><p><br><strong>NOTE</strong>: When this setting is defined, an <strong>Integration Owner</strong> must also be defined.</p></td></tr></tbody></table>
11. Click **Confirm**.

<details>

<summary>💡Are you integrating with Apono using Terraform?</summary>

If you want to integrate with Apono using Terraform, follow these steps instead of clicking **Confirm**:

1. At the top of the screen, click **View as Code**. A modal appears with the completed Terraform configuration code.
2. Click to copy the code.
3. Make any additional edits.
4. Deploy the code in your Terraform.

Refer to [Integration Config Metadata](https://docs.apono.io/metadata-for-integration-config/integration-metadata/elasticsearch) for more details about the schema definition.

</details>

#### Usage

Now that the integration is complete, you can add Elasticsearch to define the resources in an access flow. This allows requesters to access Elasticsearch indices securely based on your approval and provisioning rules.

Follow the guidance in these articles to define the resource using Elastic Cloud:

* [Define the resource (Self Serve Access Flows)](https://docs.apono.io/docs/access-flows/creating-access-flows-in-apono/self-serve-access-flows#define-the-resource)
* [Define the resource (Automatic Access Flows)](https://docs.apono.io/docs/access-flows/creating-access-flows-in-apono/automatic-access-flows#define-the-resource)