mirror of
https://github.com/elastic/logstash.git
synced 2025-04-24 14:47:19 -04:00
Update terminology used for security product
This commit is contained in:
parent
6da31eca80
commit
11df54ac6b
1 changed files with 1 additions and 1 deletions
2
docs/static/deploying.asciidoc
vendored
2
docs/static/deploying.asciidoc
vendored
|
@ -63,7 +63,7 @@ nodes. By default, Logstash uses the HTTP protocol to move data into the cluster
|
||||||
You can use the Elasticsearch HTTP REST APIs to index data into the Elasticsearch cluster. These APIs represent the
|
You can use the Elasticsearch HTTP REST APIs to index data into the Elasticsearch cluster. These APIs represent the
|
||||||
indexed data in JSON. Using the REST APIs does not require the Java client classes or any additional JAR
|
indexed data in JSON. Using the REST APIs does not require the Java client classes or any additional JAR
|
||||||
files and has no performance disadvantages compared to the transport or node protocols. You can secure communications
|
files and has no performance disadvantages compared to the transport or node protocols. You can secure communications
|
||||||
that use the HTTP REST APIs with the {shield}[Shield] plugin, which supports SSL and HTTP basic authentication.
|
that use the HTTP REST APIs by using {shield}[{security}], which supports SSL and HTTP basic authentication.
|
||||||
|
|
||||||
When you use the HTTP protocol, you can configure the Logstash Elasticsearch output plugin to automatically
|
When you use the HTTP protocol, you can configure the Logstash Elasticsearch output plugin to automatically
|
||||||
load-balance indexing requests across a
|
load-balance indexing requests across a
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue