From 11df54ac6bb211d39f2dad3c9e3778219ad8dae1 Mon Sep 17 00:00:00 2001 From: DeDe Morton Date: Mon, 4 Apr 2016 16:29:29 -0700 Subject: [PATCH] Update terminology used for security product --- docs/static/deploying.asciidoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/static/deploying.asciidoc b/docs/static/deploying.asciidoc index e57cd8555..e4d7cce4f 100644 --- a/docs/static/deploying.asciidoc +++ b/docs/static/deploying.asciidoc @@ -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 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 -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 load-balance indexing requests across a