Hi guys. Sorry if my english is bad; it's not my native language.
I am stuck on a small problem almost 3 days and I do not understand why. In fact, I try to set up TLS between the different modules (E L K).
The configuration of certificate keys at Elasticsearch level has been well established. I can only access port 9200 in HTTPS. I then wanted to configure SSL / TLS at kibana level but I can not do it.
To rebuild, I have the private key and the certficat of kibana in a folder certs. Parreil for elasticsearch.
Here is the kibana.yml configuration file:
Based on the configuration you gave, I'm not sure what the issue is, but I have a hunch. You're connecting to https://localhost:9200, but I doubt your certificates were issued for the domain: localhost. Most likely, they were issued for a specific domain or network address. Do you know how those pem files were generated?
Also, in the future, you shouldn't post any passwords here on the forum! I'd change your elastic password, just to be safe.
Good note for the confidentiality of my password and I thank you for your answer
For the creation of pem files, I first, generate a file p12 (Containing the certificate and the private key, if I do not say nonsense) for certification atoority, AC following the documentation.
Then, from each ELK module, I then generated the certiificat and the private key based on the CA.
My question is to know the necessary steps to confiigure the file kibana.yml so that I can specify the correct certificates and keys (from Elastiicearch and CA.)
I haven't personally tried connecting ELK via https over localhost, so I'm not sure if I'm leading you down the right path, but I suspect the problem is that the certificates you are using aren't trusted.
Here's something that popped up when I searched for this issue:
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.