fixing internal links and added temp anchors back

Author: eedugon

deploy-manage/deploy/cloud-on-k8s/k8s-kibana-advanced-configuration.md

@@ -12,7 +12,7 @@ If you already looked at the [Elasticsearch on ECK](elasticsearch-configuration.
 
 * [Customize the Pod configuration](#k8s-kibana-pod-configuration)
 * [Customize the product configuration](#k8s-kibana-configuration)
-* [Manage HTTP settings](k8s-kibana-http-configuration.md)
+* [Manage HTTP settings](/deploy-manage/security/secure-http-communications.md#k8s-kibana-http-configuration)
 * [Use secure settings](k8s-kibana-secure-settings.md)
 * [Install {{kib}} plugins](k8s-kibana-plugins.md)
 

deploy-manage/deploy/cloud-on-k8s/kibana-configuration.md

@@ -22,7 +22,7 @@ The following sections describe how to customize a {{kib}} deployment to suit yo
     * [Scaling out a {{kib}} deployment](k8s-kibana-advanced-configuration.md#k8s-kibana-scaling)
 
 * [Secure settings](k8s-kibana-secure-settings.md)
-* [HTTP Configuration](k8s-kibana-http-configuration.md)
+* [HTTP Configuration](/deploy-manage/security/secure-http-communications.md#k8s-kibana-http-configuration)
 
     * [Load balancer settings and TLS SANs](/deploy-manage/security/secure-http-communications.md#k8s-kibana-http-publish)
     * [Provide your own certificate](/deploy-manage/security/secure-http-communications.md#k8s-kibana-http-custom-tls)

deploy-manage/security/install-stack-demo-secure.md

@@ -16,15 +16,15 @@ Since {{stack}} 8.0, security is enabled by default, meaning that traffic betwee
 
 For traffic to be encrypted between {{es}} cluster nodes and between {{kib}} and {{es}}, SSL certificates must be created for the transport ({{es}} inter-node communication) and HTTP (for the {{es}} REST API) layers. Similarly, when setting up {{fleet-server}} you’ll generate and configure a new certificate bundle, and then {{elastic-agent}} uses the generated certificates to communicate with both {{fleet-server}} and {{es}}. The process to set things up is as follows:
 
-* [Prerequisites and assumptions](secure-your-cluster-deployment.md#install-stack-demo-secure-prereqs)
-* [Step 1: Generate a new self-signed CA certificate](secure-your-cluster-deployment.md#install-stack-demo-secure-ca)
-* [Step 2: Generate a new certificate for the transport layer](secure-your-cluster-deployment.md#install-stack-demo-secure-transport)
-* [Step 3: Generate new certificate(s) for the HTTP layer](secure-your-cluster-deployment.md#install-stack-demo-secure-http)
-* [Step 4: Configure security on additional {{es}} nodes](secure-your-cluster-deployment.md#install-stack-demo-secure-second-node)
-* [Step 5: Generate server-side and client-side certificates for {{kib}}](secure-your-cluster-deployment.md#install-stack-demo-secure-kib-es)
-* [Step 6: Install {{fleet}} with SSL certificates configured](secure-your-cluster-deployment.md#install-stack-demo-secure-fleet)
-* [Step 7: Install {{agent}}](secure-your-cluster-deployment.md#install-stack-demo-secure-agent)
-* [Step 8: View your system data](secure-your-cluster-deployment.md#install-stack-demo-secure-view-data)
+* [Prerequisites and assumptions](#install-stack-demo-secure-prereqs)
+* [Step 1: Generate a new self-signed CA certificate](#install-stack-demo-secure-ca)
+* [Step 2: Generate a new certificate for the transport layer](#install-stack-demo-secure-transport)
+* [Step 3: Generate new certificate(s) for the HTTP layer](#install-stack-demo-secure-http)
+* [Step 4: Configure security on additional {{es}} nodes](#install-stack-demo-secure-second-node)
+* [Step 5: Generate server-side and client-side certificates for {{kib}}](#install-stack-demo-secure-kib-es)
+* [Step 6: Install {{fleet}} with SSL certificates configured](#install-stack-demo-secure-fleet)
+* [Step 7: Install {{agent}}](#install-stack-demo-secure-agent)
+* [Step 8: View your system data](#install-stack-demo-secure-view-data)
 
 It should take between one and two hours to complete these steps.
 

deploy-manage/security/secure-cluster-communications.md

@@ -14,6 +14,9 @@ mapped_urls:
 % TODO: what to do about this page that doesn't exist
 % * [/raw-migrated-files/cloud-on-k8s/cloud-on-k8s/k8s-security.md](/raw-migrated-files/cloud-on-k8s/cloud-on-k8s/k8s-security.md)
 
+$$$encrypt-internode-communication$$$
+$$$generate-certificates$$$
+
 
 # Secure cluster communications
 

deploy-manage/security/secure-http-communications.md

@@ -18,6 +18,8 @@ mapped_urls:
 % Internal links rely on the following IDs being on this page (e.g. as a heading ID, paragraph ID, etc):
 
 $$$configuring-tls-browser-kib$$$
+$$$encrypt-http-communication$$$
+
 % Weird redirect in current system, not sure what to do
 
 # Secure HTTP communications

deploy-manage/security/secure-your-cluster-deployment.md

@@ -9,6 +9,26 @@ applies_to:
 
 # Secure your cluster or deployment
 
+$$$install-stack-demo-secure-agent$$$
+
+$$$install-stack-demo-secure-ca$$$
+
+$$$install-stack-demo-secure-fleet$$$
+
+$$$install-stack-demo-secure-http$$$
+
+$$$install-stack-demo-secure-kib-es$$$
+
+$$$install-stack-demo-secure-prereqs$$$
+
+$$$install-stack-demo-secure-second-node$$$
+
+$$$install-stack-demo-secure-transport$$$
+
+$$$install-stack-demo-secure-view-data$$$
+
+$$$security-configure-settings$$$
+
 
 Protecting your {{es}} cluster and the data it contains is of utmost importance. Implementing a defense in depth strategy provides multiple layers of security to help safeguard your system.
 

deploy-manage/security/using-kibana-with-security.md

@@ -6,6 +6,8 @@ mapped_urls:
   - https://www.elastic.co/guide/en/kibana/current/using-kibana-with-security.html
 ---
 
+$$$kibana-roles$$$
+
 # Configure security in {{kib}} [using-kibana-with-security]
 
 When you start {{es}} for the first time, {{stack-security-features}} are enabled on your cluster and TLS is configured automatically. The security configuration process generates a password for the `elastic` user and an enrollment token for {{kib}}. [Start the {{stack}} with security enabled](/deploy-manage/security/security-certificates-keys.md) and then enroll {{kib}} as part of the configuration process.