# HTTPS in elastic

**URL:** https://discuss.elastic.co/t/https-in-elastic/229629
**Category:** Elasticsearch
**Tags:** elastic-stack-security
**Created:** [April 24, 2020, 11:07am UTC](https://discuss.elastic.co/t/https-in-elastic/229629 "2020-04-24T11:07:29Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![carcasgon](https://avatars.discourse-cdn.com/v4/letter/c/f1d935/32.png) [@carcasgon](https://discuss.elastic.co/u/carcasgon)
#### Post date: [April 24, 2020, 11:07am UTC](https://discuss.elastic.co/t/https-in-elastic/229629/1 "2020-04-24T11:07:30Z")

</div>

Hi! I wanted to know what does elastic mean in this page:  
[_https://www.elastic.co/es/blog/configuring-ssl-tls-and-https-to-secure-elasticsearch-kibana-beats-and-logstash_](https://www.elastic.co/blog/configuring-ssl-tls-and-https-to-secure-elasticsearch-kibana-beats-and-logstash)  
when they say:

**[1-1] Configure /etc/hosts file**

**For this example our node1 has a browser installed, so kibana.local will allow access to the Kibana web page.**

#/etc/hosts file for [node1] (we need kibana.local and logstash.local)  
127.0.0.1 kibana.local logstash.local  
192.168.0.2 [node1.elastic.test.com](http://node1.elastic.test.com) node1  
192.168.0.3 [node2.elastic.test.com](http://node2.elastic.test.com) node2

What is kibana.local and elastic.local? I am really lost there, if someone knows please tell me!

By the way, I am in a Wndows system and this is explained in a linux system,

---

<div class="post-metadata">

### 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: [April 24, 2020, 1:22pm UTC](https://discuss.elastic.co/t/https-in-elastic/229629/2 "2020-04-24T13:22:53Z")

</div>

Hi,

This is just setting aliases for the hostnames `kibana.local` , `logstash.local` to point to the localhost itself so that you i.e. can access `http://kibana.local:5601` in your browser, instead of `http://localhost:5601` or `http://127.0.0.1:5601` . This is neither necessary nor necessarily a best practice for all use cases.

Blog posts usually explain a very specific use case in an easy and consumable manner, but if you don't have the same goals or environments, you are much better off with reading our [documentation](https://www.elastic.co/guide/en/elasticsearch/reference/7.6/encrypting-communications.html) than trying to half-follow a blog post where many things do not apply to you.

---

<div class="post-metadata">

### Author: ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)
#### Post date: [May 22, 2020, 1:29pm UTC](https://discuss.elastic.co/t/https-in-elastic/229629/3 "2020-05-22T13:29:45Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.
