❗️ These instructions apply only to Kibana/Elasticsearch versions 7.0 or higher. Earlier versions on Deploy did not make use of Elasaticsearch’s native authentication or encryption, so we built our own Kibana App compatible with those versions, which you can find here: aptible/docker-kibanaDeploying Kibana on Aptible is not materially different from deploying any other prepackaged software. Below we will outline the basic configuration and best practices for deploying Elastic’s official Kibana image.
aptible deploy
command:
ELASTICSEARCH_HOSTS
variable in this format:https://$HOSTNAME:$PORT/
.
📘 Specifying a Kibana image requires a specific version number tag. The latest
tag is not supported. You must specify the same version for Kibana that your Elasticsearch database is running.
You can make additional customizations using environment variables; refer to Elastic’s Kibana environment variable documentation for a list of available variables.
RELEASE_HEALTHCHECK_TIMEOUT
Configuration variable is set to 5 minutes above.
You should not scale the Kibana App to more than one container. User session information is not shared between containers, and if you scale the service to more than one container, you will get stuck in an authentication loop.