Reputation: 151
I use elasticsearch and kibana for saving and querying my data. Some good feature like RBAC
, SIEM
require ssl communication on elasticsearch with kibana. So I enable xpack.security.http.ssl.enabled
and xpack.security.transport.ssl.enabled
. Thus client requests to es must be via https.
I also have a flink cluster writing data to elasticsearch. flink & elasticsearch & kibana are running on docker swarm. It's no need for flink to authenticate with es or encrypt between traffic. I think flink can access es via http protocol and no authentication.
So, can elasticseach support http and https simultaneously for different source host?
Is it possible to selectively authenticate user requests base on source ip or host?
Plus:
Upvotes: 1
Views: 9757
Reputation: 217464
Once you enable HTTP security, all clients must be updated to communicate with the cluster via SSL, it would not make sense to have one part of the clients communicating securely and another part that don't.
If you enable TLS on the HTTP layer in Elasticsearch, then you might need to make configuration changes in other parts of the Elastic Stack and in any Elasticsearch clients that you use.
Also see what just happened a few days ago to thousands of clusters that were being left accessible to the world.
Upvotes: 3