[[ccs-tribe-clients-integrations]]
== Cross Cluster Search, Clients and Integrations

When using {ref}/modules-cross-cluster-search.html[Cross Cluster Search]
you need to take extra steps to secure communications with the connected
clusters.

* <<cross-cluster-configuring, Cross Cluster Search and Security>>

You will need to update the configuration for several clients to work with a
secured cluster:

* <<java-clients, Java Clients>>
* <<http-clients, HTTP Clients>>


{security} enables you to secure your {es} cluster. But {es} itself is only one
product within the Elastic Stack. It is often the case that other products in
the stack are connected to the cluster and therefore need to be secured as well,
or at least communicate with the cluster in a secured way:

* <<hadoop, Apache Hadoop>>
* {auditbeat-ref}/securing-beats.html[Auditbeat]
* {filebeat-ref}/securing-beats.html[Filebeat]
* {heartbeat-ref}/securing-beats.html[Heartbeat]
* {kibana-ref}/using-kibana-with-security.html[{kib}]
* {logstash-ref}/ls-security.html[Logstash]
* {metricbeat-ref}/securing-beats.html[Metricbeat]
* <<secure-monitoring, Monitoring>>
* {packetbeat-ref}/securing-beats.html[Packetbeat]
* {kibana-ref}/secure-reporting.html[Reporting]
* {winlogbeat-ref}/securing-beats.html[Winlogbeat]

include::tribe-clients-integrations/cross-cluster.asciidoc[]

include::tribe-clients-integrations/java.asciidoc[]

include::tribe-clients-integrations/http.asciidoc[]

include::tribe-clients-integrations/hadoop.asciidoc[]

include::tribe-clients-integrations/beats.asciidoc[]

include::tribe-clients-integrations/monitoring.asciidoc[]