Aerospike
Last modified on June 25, 2025
Overview
This guide describes how to add Aerospike, a distributed NoSQL database, as a datasource in the StrongDM Admin UI. A datasource consists of a database resource and the credentials used to access it.
Authentication
The Aerospike datasource type supports both no-authentication (that is, where the Username and Password fields are left blank) and password-based authentication.
TLS standard and mutual (mTLS/PKI) authentication and external authentication (LDAP) are not supported.
Supported Versions and Clients
Aerospike Server Enterprise and Standard Edition versions 5.5 through 8.0 are supported, but 6.4 or later is recommended. The Community Edition is also supported but not recommended.
Prerequisites
To add a datasource, make sure you have met the following prerequisites:
- Properly configure an account for your 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 <HOSTNAME> <PORT>Netcat command. For example, usenc -zv testdb-01.fancy.org 3000. If your gateway server can connect to this hostname, you can proceed.
-z flag to check for listeners without sending data and the -v flag to show verbose output. If you do not have Netcat, you can use a package manager such as APT (Advanced Package Tool) to install it. On Linux-based distributions, run apt-get install netcat.Add a Resource
To add your Aerospike resource to StrongDM, use the following steps.
- Log in to the StrongDM Admin UI.
- Go to Resources > Datasources.
- Click Add datasource.
- Select Aerospike as the Datasource Type and set other configuration properties for your new database resource.
- Complete all required fields.
- Click Create to save the resource.
- 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 Aerospike database.
| Property | Requirement | Description |
|---|---|---|
| Display Name | Required | Meaningful name to display the resource throughout StrongDM; exclude special characters like quotes (") or angle brackets (< or >) |
| Datasource Type | Required | Select Aerospike |
| Proxy Cluster | Required | Defaults to “None (use gateways)”; if using proxy clusters, select the appropriate cluster to proxy traffic to this resource |
| Hostname | Required | Hostname for your Aerospike resource; must be accessible to a gateway or relay |
| Port | Optional | Port to use when connecting to Aerospike; default port value is 3000 |
| Port Override | Optional | Automatically generated with a value between 1024-64999 as long as that port is not used by another resource; preferred port can be modified later under Settings > Port Overrides |
| Secret Store | Optional | Credential store location; defaults to Strong Vault; learn more about Secret Store options |
| Username | Optional | Explicit username to utilize when connecting to this resource, if using password-based authentication |
| Password | Optional | Password for the user connecting to this datasource, if using password-based authentication |
| Use Aerospike Services Alternate | Optional | When selected, enables connection to alternate service addresses and ports defined by Aerospike server configuration files |
| Resource Tags | Optional | Datasource tags consisting of key-value pairs <KEY>=<VALUE> (for example, env=dev) |
Resource status
After a resource is created, the Admin UI displays that resource as unhealthy until the health checks 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.