Add links for using Fleet Server with a proxy + small sub fixes

Author: vishaangelova

reference/fleet/add-fleet-server-cloud.md

@@ -1,12 +1,13 @@
 ---
+navigation_title: Deploy on Elastic Cloud
 mapped_pages:
   - https://www.elastic.co/guide/en/fleet/current/add-fleet-server-cloud.html
 products:
   - id: fleet
   - id: elastic-agent
 ---
 
-# Deploy on Elastic Cloud [add-fleet-server-cloud]
+# Deploy {{fleet-server}} on {{ecloud}} [add-fleet-server-cloud]
 
 To use {{fleet}} for central management, a [{{fleet-server}}](/reference/fleet/fleet-server.md) must be running and accessible to your hosts.
 
@@ -39,20 +40,18 @@ This approach might *not* be right for you if you have restrictions on connectiv
 
     For more information about hosting {{fleet-server}} on {{ece}}, refer to [](/deploy-manage/deploy/cloud-enterprise/manage-integrations-server.md).
 
-
 ::::{note}
 The TLS certificates used to secure connections between {{agent}} and {{fleet-server}} are managed by {{ecloud}}. You do not need to create a private key or generate certificates.
 ::::
 
-
 When {{es}} or {{fleet-server}} are deployed, components communicate over well-defined, pre-allocated ports. You may need to allow access to these ports. See the following table for default port assignments:
 
 | Component communication | Default port |
 | --- | --- |
-| Elastic Agent → {{fleet-server}} | 443 |
-| Elastic Agent → {{es}} | 443 |
-| Elastic Agent → Logstash | 5044 |
-| Elastic Agent → {{kib}} ({{fleet}}) | 443 |
+| {{agent}} → {{fleet-server}} | 443 |
+| {{agent}} → {{es}} | 443 |
+| {{agent}} → {{ls}} | 5044 |
+| {{agent}} → {{kib}} ({{fleet}}) | 443 |
 | {{fleet-server}} → {{kib}} ({{fleet}}) | 443 |
 | {{fleet-server}} → {{es}} | 443 |
 
@@ -61,7 +60,6 @@ If you do not specify the port for {{es}} as 443, the {{agent}} defaults to 9200
 ::::
 
 
-
 ## Setup [add-fleet-server-cloud-set-up]
 
 To confirm that an {{integrations-server}} is available in your deployment:
@@ -80,7 +78,6 @@ Don’t see the agent? Make sure your deployment includes an {{integrations-serv
 :::::
 
 
-
 ## Next steps [add-fleet-server-cloud-next]
 
 Now you’re ready to add {{agent}}s to your host systems. To learn how, see [Install {{fleet}}-managed {{agent}}s](/reference/fleet/install-fleet-managed-elastic-agent.md).

reference/fleet/add-fleet-server-kubernetes.md

@@ -1,12 +1,13 @@
 ---
+navigation_title: Deploy on Kubernetes
 mapped_pages:
   - https://www.elastic.co/guide/en/fleet/current/add-fleet-server-kubernetes.html
 products:
   - id: fleet
   - id: elastic-agent
 ---
 
-# Deploy Fleet Server on Kubernetes [add-fleet-server-kubernetes]
+# Deploy {{fleet-server}} on Kubernetes [add-fleet-server-kubernetes]
 
 ::::{note}
 If your {{stack}} is orchestrated by [ECK](/deploy-manage/deploy/cloud-on-k8s.md), we recommend to deploy the {{fleet-server}} through the operator. That simplifies the process, as the operator automatically handles most of the resources configuration and setup steps.
@@ -29,7 +30,7 @@ You can deploy {{fleet-server}} on Kubernetes and manage it yourself. In this de
 To deploy a {{fleet-server}} on Kubernetes and register it into {{fleet}} you will need the following details:
 
 * The **Policy ID** of a {{fleet}} policy configured with the {{fleet-server}} integration.
-* A **Service token**, used to authenticate {{fleet-server}} with Elasticsearch.
+* A **Service token**, used to authenticate {{fleet-server}} with {{es}}.
 * For outgoing traffic:
 
     * The **{{es}} endpoint URL** where the {{fleet-server}} should connect to, configured also in the {{es}} output associated to the policy.
@@ -61,7 +62,6 @@ This document walks you through the complete setup process, organized into the f
     * {{kib}} should be on the same minor version as {{es}}.
 
 
-
 ## Prerequisites [add-fleet-server-kubernetes-prereq]
 
 Before deploying {{fleet-server}}, you need to:
@@ -86,7 +86,6 @@ A {{fleet-server}} certificate is not required when installing the server using
 
 ::::
 
-
 If your organization already uses the {{stack}}, you may have a CA certificate that could be used to generate the new cert for the {{fleet-server}}. If you do not have a CA certificate, refer to [Generate a custom certificate and private key for {{fleet-server}}](/reference/fleet/secure-connections.md#generate-fleet-server-certs) for an example to generate a CA and a server certificate using the `elasticsearch-certutil` tool.
 
 ::::{important}
@@ -95,7 +94,6 @@ Before creating the certificate, you need to know and plan in advance the [hostn
 ::::
 
 
-
 #### [{{fleet-server}} → {{es}} output] outbound traffic flow [add-fleet-server-kubernetes-cert-outbound]
 
 In this flow, {{fleet-server}} acts as the client and {{es}} acts as the HTTPS server. For the communication to succeed, {{fleet-server}} needs to trust the CA certificate used to sign the {{es}} certificate. If your {{es}} cluster uses certificates signed by a corporate CA or multiple intermediate CAs you will need to use them during the {{fleet-server}} setup.
@@ -105,7 +103,6 @@ If your {{es}} cluster is on Elastic Cloud or if it uses a certificate signed by
 
 ::::
 
-
 In summary, you need:
 
 * A **server certificate and key**, valid for the {{fleet-server}} URL. The CA used to sign this certificate will be needed by the {{agent}} clients and the {{fleet-server}} itself.
@@ -122,7 +119,7 @@ When {{es}} or {{fleet-server}} are deployed, components communicate over well-d
 | {{fleet-server}} → {{es}} | 9200 |
 | {{fleet-server}} → {{kib}} (optional, for {{fleet}} setup) | 5601 |
 | {{agent}} → {{es}} | 9200 |
-| {{agent}} → Logstash | 5044 |
+| {{agent}} → {{ls}} | 5044 |
 | {{agent}} → {{kib}} (optional, for {{fleet}} setup) | 5601 |
 
 In Kubernetes environments, you can adapt these ports without modifying the listening ports of the {{fleet-server}} or other applications, as traffic is managed by Kubernetes `Services`. This guide includes an example where {{agent}}s connect to the {{fleet-server}} through port `443` instead of the default `8220`.
@@ -142,7 +139,6 @@ The `service token` required by the {{fleet-server}} is different from the `enro
 
 ::::
 
-
 1. In {{kib}}, open **{{fleet}} → Settings** and ensure the **Elasticsearch output** that will be used by the {{fleet-server}} policy is correctly configured, paying special attention that:
 
     * The **hosts** field includes a valid URL that will be reachable by the {{fleet-server}} Pod(s).
@@ -197,7 +193,6 @@ The `service token` required by the {{fleet-server}} is different from the `enro
     When the {{fleet-server}} installation has succeeded, the **Confirm Connection** UI will show a **Connected** status.
 
 
-
 ### {{fleet-server}} installation [add-fleet-server-kubernetes-install]
 
 
@@ -207,8 +202,8 @@ To deploy {{fleet-server}} on Kubernetes and enroll it into {{fleet}} you need t
 
 * **Policy ID** of the {{fleet}} policy configured with the {{fleet-server}} integration.
 * **Service token**, that you can generate following the [{{fleet}} preparations](#add-fleet-server-kubernetes-preparations) or manually using the [{{es}}-service-tokens command](elasticsearch://reference/elasticsearch/command-line-tools/service-tokens-command.md).
-* **{{es}} endpoint URL**, configured in both the {{es}} output associated to the policy and in the Fleet Server as an environment variable.
-* **{{es}} CA certificate file**, configured in both the {{es}} output associated to the policy and in the Fleet Server.
+* **{{es}} endpoint URL**, configured in both the {{es}} output associated to the policy and in the {{fleet-server}} as an environment variable.
+* **{{es}} CA certificate file**, configured in both the {{es}} output associated to the policy and in the {{fleet-server}}.
 * {{fleet-server}} **certificate and key** (for **Production** deployment mode only).
 * {{fleet-server}} **CA certificate file** (for **Production** deployment mode only).
 * {{fleet-server}} URL (for **Production** deployment mode only).
@@ -228,12 +223,12 @@ Adapt and change the suggested manifests and deployment strategy to your needs,
 
 * CPU and memory `requests` and `limits`. Refer to [{{fleet-server}} scalability](/reference/fleet/fleet-server-scalability.md) for more information about {{fleet-server}} resources utilization.
 * Scheduling configuration, such as `affinity rules` or `tolerations`, if needed in your environment.
-* Number of replicas, to scale the Fleet Server horizontally.
+* Number of replicas, to scale the {{fleet-server}} horizontally.
 * Use an {{es}} CA fingerprint instead of a CA file.
 * Configure other [Environment variables](/reference/fleet/agent-environment-variables.md).
 
 
-#### Installation Steps [add-fleet-server-kubernetes-install-steps]
+#### Installation steps [add-fleet-server-kubernetes-install-steps]
 
 1. Create the Secret for the {{fleet-server}} configuration.
 
@@ -558,7 +553,6 @@ The following issues may occur when {{fleet-server}} settings are missing or con
     As a workaround, consider using `https://localhost:8220` as the `FLEET_URL` for the {{fleet-server}} configuration, and ensure that `localhost` is included in the certificate’s SAN.
 
 
-
 ## Next steps [add-fleet-server-kubernetes-next]
 
 Now you’re ready to add {{agent}}s to your host systems. To learn how, refer to [Install {{fleet}}-managed {{agent}}s](/reference/fleet/install-fleet-managed-elastic-agent.md), or [Run {{agent}} on Kubernetes managed by {{fleet}}](/reference/fleet/running-on-kubernetes-managed-by-fleet.md) if your {{agent}}s will also run on Kubernetes.

reference/fleet/add-fleet-server-mixed.md

@@ -6,7 +6,7 @@ products:
   - id: elastic-agent
 ---
 
-# Deploy Fleet Server on-premises and Elasticsearch on Cloud [add-fleet-server-mixed]
+# Deploy {{fleet-server}} on-premises and {{es}} on {{ecloud}} [add-fleet-server-mixed]
 
 To use {{fleet}} for central management, a [{{fleet-server}}](/reference/fleet/fleet-server.md) must be running and accessible to your hosts.
 
@@ -44,7 +44,6 @@ To deploy a self-managed {{fleet-server}} on-premises to work with an {{ech}} de
     For more information about hosting {{fleet-server}} on {{ece}}, refer to [](/deploy-manage/deploy/cloud-enterprise/manage-integrations-server.md).
 
 
-
 ## Prerequisites [add-fleet-server-mixed-prereq]
 
 Before deploying, you need to:
@@ -64,17 +63,16 @@ This is not required when testing and iterating using the **Quick start** option
 ::::
 
 
-
 ### Default port assignments [default-port-assignments-mixed]
 
 When {{es}} or {{fleet-server}} are deployed, components communicate over well-defined, pre-allocated ports. You may need to allow access to these ports. See the following table for default port assignments:
 
 | Component communication | Default port |
 | --- | --- |
-| Elastic Agent → {{fleet-server}} | 8220 |
-| Elastic Agent → {{es}} | 443 |
-| Elastic Agent → Logstash | 5044 |
-| Elastic Agent → {{kib}} ({{fleet}}) | 443 |
+| {{agent}} → {{fleet-server}} | 8220 |
+| {{agent}} → {{es}} | 443 |
+| {{agent}} → {{ls}} | 5044 |
+| {{agent}} → {{kib}} ({{fleet}}) | 443 |
 | {{fleet-server}} → {{kib}} ({{fleet}}) | 443 |
 | {{fleet-server}} → {{es}} | 443 |
 
@@ -83,7 +81,6 @@ If you do not specify the port for {{es}} as 443, the {{agent}} defaults to 9200
 ::::
 
 
-
 ## Create a {{fleet-server}} policy [fleet-server-create-policy]
 
 First, create a {{fleet-server}} policy. The {{fleet-server}} policy manages and configures the {{agent}} running on the {{fleet-server}} host to launch a {{fleet-server}} process.
@@ -105,7 +102,6 @@ To create a {{fleet-server}} policy:
     2. It’s recommended that you also enter the *Max agents* you intend to support with this {{fleet-server}}. This can also be modified at a later stage. This will allow the {{fleet-server}} to handle the load and frequency of updates being sent to the agent and ensure a smooth operation in a bursty environment.
 
 
-
 ## Add {{fleet-server}}s [fleet-server-add-server]
 
 Now that the policy exists, you can add {{fleet-server}}s.

reference/fleet/add-fleet-server-on-prem.md

@@ -1,12 +1,13 @@
 ---
+navigation_title: Deploy on-premises and self-managed
 mapped_pages:
   - https://www.elastic.co/guide/en/fleet/current/add-fleet-server-on-prem.html
 products:
   - id: fleet
   - id: elastic-agent
 ---
 
-# Deploy on-premises and self-managed [add-fleet-server-on-prem]
+# Deploy on-premises and self-managed {{fleet-server}} [add-fleet-server-on-prem]
 
 To use {{fleet}} for central management, a [{{fleet-server}}](/reference/fleet/fleet-server.md) must be running and accessible to your hosts.
 
@@ -32,7 +33,6 @@ You can install only a single {{agent}} per host, which means you cannot run {{f
 ::::
 
 
-
 ## Compatibility [add-fleet-server-on-prem-compatibility]
 
 {{fleet-server}} is compatible with the following Elastic products:
@@ -50,7 +50,6 @@ You can install only a single {{agent}} per host, which means you cannot run {{f
     For more information about hosting {{fleet-server}} on {{ece}}, refer to [](/deploy-manage/deploy/cloud-enterprise/manage-integrations-server.md).
 
 
-
 ## Prerequisites [add-fleet-server-on-prem-prereq]
 
 Before deploying, you need to:
@@ -70,17 +69,16 @@ This is not required when testing and iterating using the **Quick start** option
 ::::
 
 
-
 ### Default port assignments [default-port-assignments-on-prem]
 
 When {{es}} or {{fleet-server}} are deployed, components communicate over well-defined, pre-allocated ports. You may need to allow access to these ports. Refer to the following table for default port assignments:
 
 | Component communication | Default port |
 | --- | --- |
-| Elastic Agent → {{fleet-server}} | 8220 |
-| Elastic Agent → {{es}} | 9200 |
-| Elastic Agent → Logstash | 5044 |
-| Elastic Agent → {{kib}} ({{fleet}}) | 5601 |
+| {{agent}} → {{fleet-server}} | 8220 |
+| {{agent}} → {{es}} | 9200 |
+| {{agent}} → {{ls}} | 5044 |
+| {{agent}} → {{kib}} ({{fleet}}) | 5601 |
 | {{fleet-server}} → {{kib}} ({{fleet}}) | 5601 |
 | {{fleet-server}} → {{es}} | 9200 |
 
@@ -89,7 +87,6 @@ Connectivity to {{kib}} on port 5601 is optional and not required at all times.
 ::::
 
 
-
 ## Add {{fleet-server}} [add-fleet-server-on-prem-add-server]
 
 A {{fleet-server}} is an {{agent}} that is enrolled in a {{fleet-server}} policy. The policy configures the agent to operate in a special mode to serve as a {{fleet-server}} in your deployment.
@@ -135,7 +132,6 @@ To add a {{fleet-server}}:
 
     ::::
 
-
     At the **Install Fleet Server to a centralized host** step, the `elastic-agent install` command installs an {{agent}} as a managed service and enrolls it in a {{fleet-server}} policy. For more {{fleet-server}} commands, refer to the [{{agent}} command reference](/reference/fleet/agent-command-reference.md).
 
 5. If installation is successful, a confirmation indicates that {{fleet-server}} is set up and connected.