From b97b17de85c34dcf925dcc1cb521d59360615265 Mon Sep 17 00:00:00 2001 From: lcawley Date: Wed, 21 Jun 2017 11:54:35 -0700 Subject: [PATCH] [DOCS] Fix link to X-Pack Reference --- 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 687a5aba1..3970273a2 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 by using {xpack}xpack-security.html[{security}], which supports SSL and HTTP basic authentication. +that use the HTTP REST APIs by using {xpack-ref}xpack-security.html[{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