Install and Setup JDK 8+
cd
yum install wget -y
wget https://download.java.net/java/GA/jdk12.0.1/69cfe15208a647278a19ef0990eea691/12/GPL/openjdk-12.0.1_linux-x64_bin.tar.gz
tar -zxvf openjdk-12.0.1_linux-x64_bin.tar.gz
export JAVA_HOME=/home/ec2-user/d/jdk-12.0.1
export PATH=$PATH:$JAVA_HOME/bin
Code language: JavaScript (javascript)
Download and Install Kibana 7.X
cd
wget https://artifacts.elastic.co/downloads/kibana/kibana-7.2.0-linux-x86_64.tar.gz
tar -xzf kibana-7.2.0-linux-x86_64.tar.gzCode language: JavaScript (javascript)
Configure Kibana 7.X
cd kibana-7.2.0-linux-x86_64/
vi config/kibana.yml
& change follwing and uncomment it.....
------
# Ip address of server where you are installing Kibana
server.host: "172.31.28.227"
# Ip address of elastic search custor client ip
elasticsearch.hosts: ["http://172.31.11.126:9200"]Code language: PHP (php)
How to start kibana service?
# Ip address of server where you are installing Kibana
server.host: "172.31.28.227"
./bin/kibana
OR
nohup ./bin/kibana &
# To see below process for the user which is starting kibana : ps -ef | grep -u user
user 23101 1 0 Mar01 ? 00:21:23 ./../node/bin/node ./../src/cliCode language: PHP (php)I’m Rajesh Kumar, a DevOps, SRE, DevSecOps, Cloud, and Platform Engineering expert passionate about sharing practical knowledge, real-world experiences, and industry best practices. I have worked at Cotocus and regularly write about technology, travel, investing, health, product reviews, and digital marketing through my various platforms.
I publish technical articles at DevOps School, travel stories at Holiday Landmark, stock market insights at Stocks Mantra, health and fitness guidance at My Medic Plus, product reviews at TrueReviewNow, and SEO and digital marketing strategies at Wizbrand.
Find Trusted Cardiac Hospitals
Compare heart hospitals by city and services — all in one place.
Explore Hospitals
The installation steps are useful, but one operational aspect that’s missing is configuration validation before exposing Kibana to users. In production, it’s a good practice to verify Elasticsearch connectivity, index health, and startup status through automated checks before allowing traffic to the Kibana UI. This prevents situations where the service is running but dashboards remain unusable because of backend connectivity issues, version mismatches, or unhealthy indices. Incorporating these validation steps into deployment automation can significantly reduce troubleshooting time and improve the reliability of Elastic Stack rollouts.