diff --git a/shield/docs/public/getting-started.asciidoc b/shield/docs/public/getting-started.asciidoc index a1d2efd907a..db2f3135424 100644 --- a/shield/docs/public/getting-started.asciidoc +++ b/shield/docs/public/getting-started.asciidoc @@ -1,4 +1,4 @@ -[[getting-started]] +[[getting-started-with-shield]] == Getting Started with Shield This getting started guide walks you through installing Shield, setting up basic authentication, and getting started with role-based @@ -32,7 +32,7 @@ NOTE: If you are using a <> of Elasticsea bin/elasticsearch ---------------------------------------------------------- -. To verify that Shield is up and running, check the startup log entries. When Shield is operating normally, the log indicates that the network transports are using Shield: +. To verify that Shield is up and running, check the startup log entries. When Shield is operating normally, the log indicates that the network transports are using Shield: + [source,shell] ---------------- diff --git a/shield/docs/public/installing-shield.asciidoc b/shield/docs/public/installing-shield.asciidoc index 0e3071b43fa..68c1e8e38b7 100644 --- a/shield/docs/public/installing-shield.asciidoc +++ b/shield/docs/public/installing-shield.asciidoc @@ -1,7 +1,7 @@ [[installing-shield]] == Installing Shield -The <> steps through a basic Shield installation. This section provides some additional information about the installation prerequisites, deployment options, and the installation process for RPM/DEB package installations. +The <> steps through a basic Shield installation. This section provides some additional information about the installation prerequisites, deployment options, and the installation process for RPM/DEB package installations. IMPORTANT: The Shield plugin must be installed on every node in the cluster and every node must be restarted after installation. Plan for a complete cluster restart before beginning the installation process. @@ -75,7 +75,7 @@ bin/plugin -i shield -u file://PATH_TO_ZIP_FILE <1> === Installing Shield on Tribe Nodes Shield supports the {ref}/modules-tribe.html[Tribe Node], which acts as a federated client across multiple clusters. When using Tribe Nodes with Shield, you must have the same Shield configuration (users, roles, user-role mappings, SSL/TLS CA) on each cluster, and on the Tribe Node itself, where security checking is primarily done. This, of course, also means -that all clusters must be running Shield. +that all clusters must be running Shield. To use a Tribe Node with Shield: diff --git a/shield/docs/public/introduction.asciidoc b/shield/docs/public/introduction.asciidoc index 8bfcfd74589..9cd26ba98b2 100644 --- a/shield/docs/public/introduction.asciidoc +++ b/shield/docs/public/introduction.asciidoc @@ -42,7 +42,7 @@ Keeping a system secure takes vigilance. By using Shield to maintain an audit tr [float] === Where to Go Next -* <> steps through how to install and start using Shield for basic authentication. +* <> steps through how to install and start using Shield for basic authentication. * <> provides more information about how Shield supports user authentication, authorization, and encryption. * <> shows you how to interact with an Elasticsearch cluster protected by Shield.