Deploy Kibana
Kibana dashboards with a secured, persistent Elasticsearch 9 node
Just deployed
Elasticsearch
Just deployed
/usr/share/elasticsearch/data
Deploy and Host Kibana on Railway
Kibana is Elastic's open-source web interface for Elasticsearch. You use it to search and explore data in Discover, build dashboards and visualizations, set up alerting rules, manage indices and users, and run queries in Dev Tools. This template deploys Kibana 9.5.6 together with its own Elasticsearch 9.5.6 node.
About Hosting Kibana
Kibana needs an Elasticsearch cluster of the same version, a login, and encryption keys that stay the same across restarts. This template runs both services from one GitHub repo with images pinned by version and digest. Elasticsearch runs as a single node with security on, keeps its data on a Railway volume, and is reachable only over the private network. Kibana gets a public HTTPS domain, connects as the built-in kibana_system user, and stores its dashboards and settings in Elasticsearch. Passwords and encryption keys are generated at deploy time. After deploying, open Kibana's domain and log in as elastic with the ELASTIC_PASSWORD from the Elasticsearch service's Variables tab. The first start takes 2 to 4 minutes.
Common Use Cases
- Searching and exploring logs, metrics and events stored in Elasticsearch
- Building dashboards and alerts for applications and infrastructure
- Managing Elasticsearch indices, users, roles and API keys from a web UI
Dependencies for Kibana Hosting
- Elasticsearch 9.5.6 (included, single node with a volume)
- About 2 GB of memory for Elasticsearch (1 GB heap) and 1 GB for Kibana
Deployment Dependencies
- Kibana source and releases
- Template repo: aalfath/kibana-railway-template
- Kibana Docker documentation
- Elasticsearch Docker documentation
Implementation Details
- Kibana:
elastic/kibana:9.5.6, health check/api/status, no volume needed (its data lives in Elasticsearch). Kibana's instance ID is pinned to the Railway service ID, so it stays the same across redeploys. - Elasticsearch:
elastic/elasticsearch:9.5.6, data on a volume at/usr/share/elasticsearch/data, heap set byES_JAVA_OPTS(default 1 GB). Anonymous requests can read/_cluster/health(the health check) and nothing else. - The
elasticpassword is stored on the first start. To change it later, use Kibana (Stack Management, Users), not the variable. - Don't change the three
XPACK_*_ENCRYPTIONKEYvariables after the first start, or saved connector secrets can't be decrypted. - To send data from outside Railway, add a public domain to the Elasticsearch service and use an API key or a dedicated user.
- Updates: new versions land on the template repo's
mainbranch with a changelog entry, and Railway shows you an "update available" notice. Apply it to both services together, since Kibana and Elasticsearch must run the same version.
Why Deploy Kibana on Railway?
Railway is a singular platform to deploy your infrastructure stack. Railway will host your infrastructure so you don't have to deal with configuration, while allowing you to vertically and horizontally scale it.
By deploying Kibana on Railway, you are one step closer to supporting a complete full-stack application with minimal burden. Host your servers, databases, AI agents, and more on Railway.
Template Content
Elasticsearch
aalfath/kibana-railway-template
