Elasticsearch - 7.0 or later

️ Warning

The information on this page pertains to support Elasticsearch versions 7.0 and later. Please refer to Elasticsearch for information about earlier versions.

Connecting to Elasticsearch

Elasticsearch is accessible over HTTPS, with Elasticsearch's native authentication mechanism.

The "aptible" user provided by the Database Credentials is the only user available by default, and is configured with the Elasticsearch Role of "superuser". You may manage the password of any Elasticsearch Built-in user if you wish, and otherwise manage all aspects of user creation and permissions, with the exception of the "aptible" user.

📘

Tip

Elasticsearch databases deployed on Aptible Deploy use a valid certificate for their host, so you're encouraged to verify the certificate when connecting.

Subscription Features

Formerly referred to as X-pack features, your Elastic Stack subscription will determine the features available in your Deploy Elasticsearch Database. By default, you will have the "Basic" features. If you purchase a license from Elastic, you may update your license at any time.

Plugins

Some Elasticsearch plugins may be installed on-request. Contact Aptible Support if you need a particular plugin.

Configuration

Elasticsearch Databases can be configured with Elasticsearch's Cluster Update Settings API. Changes made to "persistent" settings will persist across Database restarts.

Deploy will automatically set the JVM heap size to 50% of the container's memory allocation, per Elastic's recommendation.

Kibana

You can easily deploy Elastic's official Kibana image as an App on Aptible Deploy. Please see our tutorial that covers Running Kibana.

Log Rotation

If you're using Elasticsearch to hold log data, you'll almost certainly be creating new indexes periodically - by default, Logstash or our Log Drains will do so daily. This will necessarily mean that as time passes, you'll need more and more disk space, but also less obviously, more and more RAM. Elasticsearch allocates RAM on a per-index basis, and letting your logs retention grow unchecked will almost certainly lead to fatal issues when the database runs out of RAM or disk space.

To avoid this, we recommend using a combination of Elasticsearch's native features to ensure you don't accumulate too many open indexes:

Please see our tutorial that covers Elasticsearch Log Rotation for more information.

Connection Security

Aptible Deploy Elasticsearch Databases support connections via the following protocols:

  • For all Elasticsearch versions 7.0 and later: , TLSv1.1, TLSv1.2

Did this page help you?