Elasticsearch

Create an integration to manage access to an Elasticsearch instance

Suggest Edits

Elasticsearch is a distributed, RESTful search and analytics engine designed for horizontal scalability, reliability, and real-time search. It enables users to store, search, and analyze big volumes of data quickly and in near real-time. Elasticsearch is widely used for log and event data analysis, full-text search, and complex searches across large datasets.

Through this integration, Apono helps you securely manage access to your Elasticsearch instance.


Prerequisites

ItemDescription
Apono ConnectorOn-prem connection serving as a bridge between an Elasticsearch instance and Apono:

Apono HTTP ProxyAuthorization controls to manage Elasticsearch

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.

Integrate Elasticsearch

Elasticsearch tile

Elasticsearch tile


Follow these steps to complete the integration:

  1. On the Catalog tab, click Elasticsearch. The Connect integration page appears.
  2. Under Discovery, click Next. The Apono connector section expands.
  3. From the dropdown menu, select a connector.

    💡

    If the desired connector is not listed, click + Add new connector and follow the instructions for creating a connector (AWS, Azure, GCP, Kubernetes).

  4. Click Next. The Integration Config section expands.
  5. Define the Integration Config settings.
    Setting Description
    Integration Name Unique, alphanumeric, user-friendly name used to identify this integration when constructing an access flow
    Proxy Address Elasticsearch proxy address
    Clusters Array of Elasticsearch clusters

    Example: [{"name":"cluster-1","hostname":"cluster-1.customer.com:9200"}]

  1. Click Next. The Get more with Apono section expands.
  2. Define the Get more with Apono settings.
    Setting Description
    Custom Access Details (Optional) Instructions explaining how to access this integration's resources

    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 400 characters.

    To view the message as it appears to end users, click Preview.

    NOTE: You can also add the custom_access_details parameter to the apono_integration schema using Terraform. For more information, learn how to integrate with Apono in the Terraform Registry.
    Integration Owner (Optional) Fallback approver if no resource owner is found

    Follow these steps to define one or several integration owners:
    1. From the Attribute dropdown menu, select User or Group under the relevant identity provider (IdP) platform.
    2. From the Value dropdown menu, select one or multiple users or groups.

    NOTE: When Resource Owner is defined, an Integration Owner must be defined.
    Resource Owner (Optional) Group or role responsible for managing access approvals or rejections for the resource

    Follow these steps to define one or several resource owners:
    1. Enter a Key name. This value is the name of the tag created in your cloud environment.

    2. From the Attribute dropdown menu, select an attribute under the IdP platform to which the key name is associated.

      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.

    NOTE: When this setting is defined, an Integration Owner must also be defined.

  1. Click Confirm.

Now that you have completed this integration, you can create access flows that grant permission to your Elasticsearch instance.

Updated 2 days ago

What’s Next