From 90b1dec14b36989f093f93200ac11ffec00b027a Mon Sep 17 00:00:00 2001
From: lcawley <lcawley@elastic.co>
Date: Thu, 15 Feb 2018 12:31:48 -0800
Subject: [PATCH] [DOCS] Fixed broken TLS link

Original commit: elastic/x-pack-elasticsearch@34ec651dc930a3cb5ac66f24b39b30852d38f9fd
---
 .../security/securing-communications/setting-up-ssl.asciidoc   | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/docs/en/security/securing-communications/setting-up-ssl.asciidoc b/docs/en/security/securing-communications/setting-up-ssl.asciidoc
index 0c381c454d6..ad2548f73f4 100644
--- a/docs/en/security/securing-communications/setting-up-ssl.asciidoc
+++ b/docs/en/security/securing-communications/setting-up-ssl.asciidoc
@@ -18,7 +18,8 @@ applicable to your cluster.
 . Configure each node in the cluster to identify itself using its signed
 certificate and enable TLS on the transport layer. You can also optionally
 enable TLS on the HTTP layer. See
-{ref}/configuring-tls.html#enable-ssl[Enabling TLS on {es} Nodes].
+{ref}/configuring-tls.html#tls-transport[Encrypting Communications Between Nodes in a Cluster] and
+{ref}/configuring-tls.html#tls-http[Encrypting HTTP Client Communications]. 
 
 . Configure {monitoring} to use encrypted connections. See <<secure-monitoring>>.