I'm following a tutorial you provide as part of your "learn at home" initiative called "Fundamentals of Securing Elasticsearch". I'm actually following along in my own environment. I have a AWS workspace setup and one EC2 instance running ELK.
I have so far done the following successfully...
- Configured elasticsearch and kibana for their default ports and localhost
- Configured for single node
- Setup built-in uses w/
- Added the built-in
kibanauser to the kibana keystore
- Verified security was working by issuing a curl request without credentials which caused a
security_exceptionas it should
elasticuser was working issuing a curl request with it's credentials which worked perfectly
My two configuration files at this point look like the following...
server.port: 5601 server.host: "127.0.0.1" elasticsearch.hosts: ["http://127.0.0.1:9200"]
path.data: /var/lib/elasticsearch path.logs: /var/log/elasticsearch bootstrap.memory_lock: true network.host: 127.0.0.1 http.port: 9200 discovery.type: "single-node" xpack.security.enabled: true
At this point I wanted to test the Kibana log-in page with the
elastic user. However, I wanted to use a brower from my AWS workspace to access Kibana. The only setting I changed to test this out was
server.host: 127.0.0.1 in the Kibana config to be
server.host: "172.32.xx.xx" where
172.32.xx.xx is my EC2 IP. All other settings in the kibana and elasticsearch configs stayed the same for this test.
I restarted both services then opened up a browser in my AWS workspace and navigated to
http://172.32.xx.xx:5601. The webpage just displayed a blank white screen and at the bottom indicated a "Waiting for 172.32.xx.xx" status. I waited for 5 minutes but nothing happened.
I noticed my EC2 instance was kind of hung so I had to restart my EC2 instance which was weird. After the EC2 restarted I thought I would try disabling xpack
xpack.security.enabled: false and then see what would happen by trying to access Kibana from my browser again in my AWS workspace. This time it worked and the kibana home screen appeared.
Why can't I bind Kibana to my EC2 IP
server.host: "172.32.xx.xx" with xpack enabled and access the Kibana login page from a browser in my AWS workspace?