However, When we run elasticsearch as a single node it generates some default certificates which we can find by getting inside the container as shown below.
My question is how can we use these certs and keys to enable HTTPS on elasticsearch also is it possible to use the same key and cert for kibana, logstash, and beats for secure communication over HTTPS?
Note: I am running elk stack in docker and using the latest version.
Thank you for your response. I have already enabled https using the medium link but I am confused about the certificates generated by elasticsearch when I run elasticsearch using docker run command it generates those three certificates as mention in the title of the topic as well as shown in the image. The medium link provides a different way to enable https. I am asking how can I use the certificates generated by elasticsearch to enable https. i.e http_ca.crt , transport.p12 and http.p12
So basically, if you follow the elastic document given by me, or the 3 certificates which are generated for you are the certificates which are self signed by elastic.
And the way it's shown in the medium is also the same but using a .yml file or you can say using a configuration file.
Both are generated using the elasticsearch-certutil only if you see the command.
Basically this type of generation is used when you want to give a custom name to the cert file or when you wanted to add multiple dns names in the cert or when you need to generate .csr files and get them signed by other Signing Autorities.
As of now, as you've enabled https, that should be fine.
The generated certs can be ignored in your case currently.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.