Production-ready single-node Elasticsearch with Kibana, using official images. Password and SSL enabled by default.
This template deploys a single-node Elasticsearch + Kibana stack using official Elastic images. Password authentication is enabled out of the box, and HTTPS is provided by Zeabur's edge for the public domains.
elastic userNote: Inter-service traffic between Kibana and Elasticsearch is plain HTTP inside the project network. The cluster is single-node, so transport-layer TLS is disabled. If you need full end-to-end TLS or a multi-node cluster, use a different template.
ELK does not provide a one-click deployment. Follow these steps to finish setting up Kibana:
elasticsearch service and create a service-account token for Kibana:
$ ./bin/elasticsearch-service-tokens create elastic/kibana kibana
SERVICE_TOKEN elastic/kibana/kibana = <your-service-token>
ELASTICSEARCH_SERVICEACCOUNTTOKEN environment variable on the kibana service.kibana service.kibana service and generate the encryption keys:
$ bin/kibana-encryption-keys generate
The output prints three values that should be set as environment variables on the kibana service:
XPACK_ENCRYPTEDSAVEDOBJECTS_ENCRYPTIONKEY — encrypts stored objects (dashboards, visualizations)XPACK_REPORTING_ENCRYPTIONKEY — encrypts saved reportsXPACK_SECURITY_ENCRYPTIONKEY — encrypts session informationkibana service.kibana service.https://<your-elasticsearch-domain> (Zeabur edge terminates TLS — no port suffix needed).https://<your-kibana-domain> — the web-based visualization interface.Check the instructions section of the Kibana service to see the auto-generated credentials.
Log in to Kibana with the elastic username and the auto-generated password to explore, visualize, and manage your Elasticsearch data.