mirror of
https://github.com/elastic/elasticsearch.git
synced 2025-04-25 23:57:20 -04:00
255c9a7f95
**Problem:** For historical reasons, source files for the Elasticsearch Guide's security, watcher, and Logstash API docs are housed in the `x-pack/docs` directory. This can confuse new contributors who expect Elasticsearch Guide docs to be located in `docs/reference`. **Solution:** - Move the security, watcher, and Logstash API doc source files to the `docs/reference` directory - Update doc snippet tests to use security Rel: https://github.com/elastic/platform-docs-team/issues/208
29 lines
1.1 KiB
Text
29 lines
1.1 KiB
Text
[role="xpack"]
|
|
[[security-clients-integrations]]
|
|
== Securing clients and integrations
|
|
|
|
You will need to update the configuration for several <<http-clients,clients>>
|
|
to work with a secured {es} cluster.
|
|
|
|
The {es} {security-features} enable you to secure your {es} cluster. But
|
|
{es} itself is only one product within the {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-auditbeat.html[Auditbeat]
|
|
* {filebeat-ref}/securing-filebeat.html[Filebeat]
|
|
* {heartbeat-ref}/securing-heartbeat.html[Heartbeat]
|
|
* {kibana-ref}/using-kibana-with-security.html[{kib}]
|
|
* {logstash-ref}/ls-security.html[Logstash]
|
|
* {metricbeat-ref}/securing-metricbeat.html[Metricbeat]
|
|
* <<secure-monitoring>>
|
|
* {packetbeat-ref}/securing-packetbeat.html[Packetbeat]
|
|
* {kibana-ref}/secure-reporting.html[Reporting]
|
|
* {winlogbeat-ref}/securing-winlogbeat.html[Winlogbeat]
|
|
|
|
include::http.asciidoc[]
|
|
|
|
include::hadoop.asciidoc[]
|
|
|
|
include::monitoring.asciidoc[]
|