SSL Pre-existing wild card cert and AWS

Search Guard
1

I have beats talking to logstash using an existing wildcard SSL certificate from a third party. I’m running the entire stack in AWS. I want to use search guard to protect logstash to elasticsearch, elasticsearch to elasticsearch, and kibana to elasticsearch communications.

I want to continue to use the wildcard certificate. Do a set of instructions exist on the proper setup for creating the keystore and truststore using a wildcard? I don’t want to enter individual keys into the keystore for each host, as we utilize auto scaling heavily.

2

I don't think that wildcard certs need a special setup, so you should find all you need here http://floragunncom.github.io/search-guard-ssl-docs/
What is your preferred tool to setup the key and truststores (openssl or keytool?)

···

Am 17.02.2017 um 17:54 schrieb Joel S <jjshoe@gmail.com>:

I have beats talking to logstash using an existing wildcard SSL certificate from a third party. I'm running the entire stack in AWS. I want to use search guard to protect logstash to elasticsearch, elasticsearch to elasticsearch, and kibana to elasticsearch communications.

I want to continue to use the wildcard certificate. Do a set of instructions exist on the proper setup for creating the keystore and truststore using a wildcard? I don't want to enter individual keys into the keystore for each host, as we utilize auto scaling heavily.

--
You received this message because you are subscribed to the Google Groups "Search Guard" group.
To unsubscribe from this group and stop receiving emails from it, send an email to search-guard+unsubscribe@googlegroups.com.
To post to this group, send email to search-guard@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/search-guard/32a7a588-1abd-40c6-b815-393048fa6a27%40googlegroups.com\.
For more options, visit https://groups.google.com/d/optout\.