honeymoose/OpenSearch
1
0
Fork 0
mirror of https://github.com/honeymoose/OpenSearch.git synced 2025-02-22 21:05:23 +00:00
Code Issues Packages Projects Releases Wiki Activity

[DOCS] Fix typos

Browse Source
This commit is contained in:
lcawl 2018-12-19 15:28:25 -08:00
parent ecb822c666
commit 8b8121279a
2 changed files with 9 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
docs/reference/security/securing-communications/separating-node-client-traffic.asciidoc
View File

@ -2,13 +2,14 @@
[[separating-node-client-traffic]]
=== Separating node-to-node and client traffic
Elasticsearch has the feature of so called {ref}/modules-transport.html[TCP transport profiles]
that allows it to bind to several ports and addresses. {es} {security-features} extends on this
functionality to enhance the security of the cluster by enabling the separation
of node-to-node transport traffic from client transport traffic. This is important
if the client transport traffic is not trusted and could potentially be malicious.
To separate the node-to-node traffic from the client traffic, add the following
to `elasticsearch.yml`:
Elasticsearch has the feature of so called
{ref}/modules-transport.html[TCP transport profiles]
that allows it to bind to several ports and addresses. The {es}
{security-features} extend on this functionality to enhance the security of the
cluster by enabling the separation of node-to-node transport traffic from client
transport traffic. This is important if the client transport traffic is not
trusted and could potentially be malicious. To separate the node-to-node traffic
from the client traffic, add the following to `elasticsearch.yml`:
[source, yaml]
--------------------------------------------------

2
x-pack/docs/en/security/ccs-clients-integrations/monitoring.asciidoc
View File

@ -1,7 +1,7 @@
[[secure-monitoring]]
=== Monitoring and security
The <<xpack-monitoring,{stack} {monitor-features}>> consists of two components:
The <<xpack-monitoring,{stack} {monitor-features}>> consist of two components:
an agent that you install on on each {es} and Logstash node, and a Monitoring UI
in {kib}. The monitoring agent collects and indexes metrics from the nodes
and you visualize the data through the Monitoring dashboards in {kib}. The agent