Elastic Cloud

Streamline just-in-time access to Elastic Cloud resources via Apono

Elastic Cloud is a fully managed Elasticsearch service that allows organizations to deploy, search, and analyze data in real time. Integrating Elastic Cloud with Apono enables automated just-in-time access to Elastic Cloud resources based on request workflows and time-bound policies. This approach ensures secure access provisioning while enforcing least-privilege principles.

This guide explains how to integrate Elastic Cloud with Apono’s UI.

Prerequisites

Item
Description

Elastic Cloud API key

Unique key generated in Elastic Cloud to authenticate connection with Apono

Learn how to generate an API key with Elastic Cloud.

NOTE: For the key to authenticate an integration with Apono, you must provision it with the Organization owner role.

Elastic organization ID

Unique identifier for your Elastic Cloud organization

Apono connector

On-prem connection serving as a bridge between your Elastic Cloud instance and Apono:

Learn how to update an existing AWS, Azure, GCP, or Kubernetes connector.

Apono secret

Value generated with the credentials of the user you create Create your secret based on your Elastic Cloud API account key and user key:

  • "api_key": <ELASTIC_API_KEY>

Apono does not store credentials. The Apono Connector uses the secret to communicate with services in your environment and separate the Apono web app from the environment for maximal security.

Integrate Elastic Cloud

Elastic Cloud resource tile

You can also use the steps below to integrate with Apono using Terraform.

In step 10, instead of clicking Confirm, follow the Are you integrating with Apono using Terraform? guidance.

Follow these steps to complete the integration:

  1. On the Catalog tab, click Elastic Cloud. The Connect Integration page appears.

  2. Under Discovery, click Next. The Apono connector section expands.

  3. 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.

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

  1. Click Next. The Integration Config section expands.

  2. Define the Integration Config settings.

    Setting
    Description

    Integration Name

    Unique, alphanumeric, user-friendly name used to identify this integration when constructing an access flow

    Organization ID

    Unique identifier for your Elastic Cloud organization

  3. Click Next. The Secret Store section expands.

  4. Associate the secret or credentials.

If you select the Apono secret manager, enter the value of your Elastic Cloud API Key.

  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.

    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.

  3. Click Confirm.

💡 Are you integrating with Apono using Terraform?

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 for more details about the schema definition.

Usage

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

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

PreviousMariaDBNextNetwork Management

Last updated

Was this helpful?