# Securing ELK **URL:** \ **Category:** Elasticsearch\ **Created:** [October 23, 2020, 7:37pm UTC](https://discuss.elastic.co/t/securing-elk/253175 "2020-10-23T19:37:20Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![jcor](https://avatars.discourse-cdn.com/v4/letter/j/8797f3/32.png) [@jcor](https://discuss.elastic.co/u/jcor)\ **Post date:** [October 23, 2020, 7:37pm UTC](https://discuss.elastic.co/t/securing-elk/253175/1 "2020-10-23T19:37:20Z")
Hi all, I'm working on securing my lab elk stack and running into a roadblock. I've been following this guide very closely [https://www.elastic.co/blog/configuring-ssl-tls-and-https-to-secure-elasticsearch-kibana-beats-and-logstash#enable-tls-kibana](https://www.elastic.co/blog/configuring-ssl-tls-and-https-to-secure-elasticsearch-kibana-beats-and-logstash#enable-tls-kibana) and parts of the stack like to throw a fit about the cert. The only step I havent followed to a T is the instance.yml section. My home lab setup is using hostnames such as elastic, logstash and kibana which I put in the instance.yml config. I also dont have multiple elastic nodes as I am trying to become familiar with the basics before going up a level so to speak. The most common error(s) seem to revolve around the ip not being in the cert (does not match the certificate subject provided by the peer ). Does anyone have a better guide? I've gotten elastic and kibana to communicate through tls and https but not logstash. Any resources/tips would be appreciated I'm fairly new to cert signing which also doesnt help my problem. Thanks! ---
**Author:** ![ikakavas](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ikakavas/32/34430_2.png) [@ikakavas](https://discuss.elastic.co/u/ikakavas)\ **Post date:** [October 23, 2020, 7:50pm UTC](https://discuss.elastic.co/t/securing-elk/253175/2 "2020-10-23T19:50:50Z")
Blog posts are generally nice to get you the general idea or when your use case is _exactly_ the same as the one described in the post. For all other cases, you should by much better off reading the actual documentation. See [here](https://www.elastic.co/guide/en/logstash/current/ls-security.html#ls-http-ssl) for example ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [November 20, 2020, 7:50pm UTC](https://discuss.elastic.co/t/securing-elk/253175/3 "2020-11-20T19:50:55Z")
Closed on November 20, 2020, 7:50pm UTC This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.