Elasticsearch

Last modified on February 11, 2025

Overview

A datasource consists of a resource and the credentials used to access it. This guide describes how to add Elasticsearch as a datasource in the StrongDM Admin UI.

Prerequisites

To add a datasource, make sure you have met the following prerequisites:

  • Properly configure an account for your database resource. If you choose to store credentials for the resource with StrongDM, have those credentials ready. When not using StrongDM, set up a Secret Store integration and be able to enter the location of the secrets required to access the resource.
  • The hostname or endpoint you enter for your resource must be accessible by at least one gateway or relay. To verify this, log in to the gateway or relay and use the nc -zv <YOUR_HOSTNAME> <YOUR_PORT> Netcat command. For example, use nc -zv testdb-01.fancy.org 3306. If your gateway server can connect to this hostname, you can proceed.

Add a Datasource

To add your Elasticsearch database as a StrongDM resource, use the following steps.

  1. Log in to the StrongDM Admin UI.
  2. Go to Resources > Datasources.
  3. Click Add datasource.
  4. Select Elasticsearch as the Datasource Type and set other configuration properties for your new database resource.
  5. Complete all required fields.
  6. Click Create to save the resource.
  7. Click the resource name to view status, diagnostic information, and setting details.

Resource properties

Configuration properties are visible when you add a datasource or when you click to view its settings. The following table describes the settings available for your Elasticsearch database.

PropertyRequirementDescription
Display NameRequiredMeaningful name to display the resource throughout StrongDM; exclude special characters like quotes (") or angle brackets (< or >)
Datasource TypeRequiredSelect Elasticsearch
HostnameRequiredHostname for your resource; must be accessible to a gateway or relay; should not include http:// or https:// for Elastic Cloud deployments
PortRequiredPort to use when connecting to Elasticsearch; default port value is 9200
Port OverrideRead onlyAutomatically generated with a value between 1024-59999 as long as that port is not used by another resource; preferred port can be modified later under Settings > Port Overrides
Healthcheck DatabaseRequiredDatabase name you would like to connect to specifically for healthchecks from StrongDM
Secret StoreOptionalCredential store location; defaults to Strong Vault; learn more about Secret Store options
UsernameRequiredUsername to utilize when connecting to this datasource; displays when Secret Store integration is not configured for your organization or when StrongDM serves as the Secret Store type
Username (path)RequiredPath to the secret in your Secret Store location (for example, path/to/credential?key=optionalKeyName where key argument is optional); required when using a non-StrongDM Secret Store type
PasswordRequiredPassword for the user connecting to this datasource; displays when Secret Store integration is not configured for your organization or when StrongDM serves as the Secret Store type
Password (path)RequiredPath to the secret in your Secret Store location (for example, path/to/credential?key=optionalKeyName where key argument is optional); required when using a non-StrongDM Secret Store type
TLS RequiredOptionalWhen selected, requires TLS for connections to this resource
Resource TagsOptionalDatasource tags consisting of key-value pairs <KEY>=<VALUE> (for example, env=dev)

Secret Store options

By default, datasource credentials are stored in StrongDM. However, these credentials can also be saved in a secrets management tool.

Non-StrongDM options appear in the Secret Store dropdown if they are created under Network > Secret Stores. When you select another Secret Store type, its unique properties display. For more details, see Configure Secret Store Integrations.

Resource status

After a resource is created, the Admin UI displays that resource as unhealthy until the healthchecks run successfully. When the resource is ready, the Health icon indicates a positive, green status.

When the resource does not display a positive status, click the resource name to go to the Diagnostics tab and check for errors.

Troubleshooting

For Elastic Cloud deployments:

  • Ensure that traffic filters are configured in order to allow traffic from StrongDM. See the Ports Guide for more information about ports used for StrongDM traffic.
  • To test that StrongDM can authenticate to your resource, try the following command, replacing the placeholders with your resource’s values:
curl -u "<USERNAME>:<PASSWORD>" -X GET "<HOSTNAME>"
Top