upd links

Signed-off-by: bmorelli25 <[email protected]>

Author: bmorelli25

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

@@ -92,7 +92,7 @@ spec:
 * `xpack.fleet.agents.elasticsearch.hosts` must point to the {{es}} cluster where {{agents}} should send data. For ECK-managed {{es}} clusters ECK creates a Service accessible through `https://ES_RESOURCE_NAME-es-http.ES_RESOURCE_NAMESPACE.svc:9200` URL, where `ES_RESOURCE_NAME` is the name of {{es}} resource and `ES_RESOURCE_NAMESPACE` is the namespace it was deployed within. See [Storing local state in host path volume](configuration-examples-standalone.md#k8s_storing_local_state_in_host_path_volume) for details on adjusting this field when running agent as non-root as it becomes required.
 * `xpack.fleet.agents.fleet_server.hosts` must point to {{fleet-server}} that {{agents}} should connect to. For ECK-managed {{fleet-server}} instances, ECK creates a Service accessible through `https://FS_RESOURCE_NAME-agent-http.FS_RESOURCE_NAMESPACE.svc:8220` URL, where `FS_RESOURCE_NAME` is the name of {{agent}} resource with {{fleet-server}} enabled and `FS_RESOURCE_NAMESPACE` is the namespace it was deployed in.
 * `xpack.fleet.packages` are required packages to enable {{fleet-server}} and {{agents}} to enroll.
-* `xpack.fleet.agentPolicies` policies are needed for {{fleet-server}} and {{agents}} to enroll to, check {{fleet-guide}}/agent-policy.html for more information.
+* `xpack.fleet.agentPolicies` policies are needed for {{fleet-server}} and {{agents}} to enroll to, check https://www.elastic.co/guide/en/fleet/current/agent-policy.html for more information.
 
 
 ## Set referenced resources [k8s-elastic-agent-fleet-configuration-setting-referenced-resources]

deploy-manage/deploy/cloud-on-k8s/logstash-plugins.md

@@ -7,7 +7,7 @@ mapped_pages:
 
 # Logstash plugins [k8s-logstash-plugins]
 
-The power of {{ls}} is in the plugins--{{logstash-ref}}/input-plugins.html[inputs], [outputs](https://www.elastic.co/guide/en/logstash/current/output-plugins.html), [filters,](https://www.elastic.co/guide/en/logstash/current/filter-plugins.html) and [codecs](https://www.elastic.co/guide/en/logstash/current/codec-plugins.html).
+The power of {{ls}} is in the plugins--https://www.elastic.co/guide/en/logstash/current/input-plugins.html[inputs], [outputs](https://www.elastic.co/guide/en/logstash/current/output-plugins.html), [filters,](https://www.elastic.co/guide/en/logstash/current/filter-plugins.html) and [codecs](https://www.elastic.co/guide/en/logstash/current/codec-plugins.html).
 
 In {{ls}} on ECK, you can use the same plugins that you use for other {{ls}} instances—​including Elastic-supported, community-supported, and custom plugins. However, you may have other factors to consider, such as how you configure your {{k8s}} resources, how you specify additional resources, and how you scale your {{ls}} installation.
 

deploy-manage/tools/snapshot-and-restore/azure-repository.md

@@ -73,15 +73,15 @@ In progress snapshot or restore jobs will not be preempted by a **reload** of th
 
 ## Client settings [repository-azure-client-settings]
 
-The following list describes the available client settings. Those that must be stored in the keystore are marked as ({{ref}}/secure-settings.html[Secure], [reloadable](../../security/secure-settings.md#reloadable-secure-settings)); the other settings must be stored in the `elasticsearch.yml` file. The default `CLIENT_NAME` is `default` but you may configure a client with a different name and specify that client by name when registering a repository.
+The following list describes the available client settings. Those that must be stored in the keystore are marked as (https://www.elastic.co/guide/en/elasticsearch/reference/current/secure-settings.html[Secure], [reloadable](../../security/secure-settings.md#reloadable-secure-settings)); the other settings must be stored in the `elasticsearch.yml` file. The default `CLIENT_NAME` is `default` but you may configure a client with a different name and specify that client by name when registering a repository.
 
-`azure.client.CLIENT_NAME.account` ({{ref}}/secure-settings.html[Secure], [reloadable](../../security/secure-settings.md#reloadable-secure-settings))
+`azure.client.CLIENT_NAME.account` (https://www.elastic.co/guide/en/elasticsearch/reference/current/secure-settings.html[Secure], [reloadable](../../security/secure-settings.md#reloadable-secure-settings))
 :   The Azure account name, which is used by the repository’s internal Azure client. This setting is required for all clients.
 
 `azure.client.CLIENT_NAME.endpoint_suffix`
 :   The Azure endpoint suffix to connect to. The default value is `core.windows.net`.
 
-`azure.client.CLIENT_NAME.key` ({{ref}}/secure-settings.html[Secure], [reloadable](../../security/secure-settings.md#reloadable-secure-settings))
+`azure.client.CLIENT_NAME.key` (https://www.elastic.co/guide/en/elasticsearch/reference/current/secure-settings.html[Secure], [reloadable](../../security/secure-settings.md#reloadable-secure-settings))
 :   The Azure secret key, which is used by the repository’s internal Azure client. Alternatively, use `sas_token`.
 
 `azure.client.CLIENT_NAME.max_retries`
@@ -96,7 +96,7 @@ The following list describes the available client settings. Those that must be s
 `azure.client.CLIENT_NAME.proxy.type`
 :   Register a proxy type for the client. Supported values are `direct`, `http`, and `socks`. For example: `azure.client.default.proxy.type: http`. When `proxy.type` is set to `http` or `socks`, `proxy.host` and `proxy.port` must also be provided. The default value is `direct`.
 
-`azure.client.CLIENT_NAME.sas_token` ({{ref}}/secure-settings.html[Secure], [reloadable](../../security/secure-settings.md#reloadable-secure-settings))
+`azure.client.CLIENT_NAME.sas_token` (https://www.elastic.co/guide/en/elasticsearch/reference/current/secure-settings.html[Secure], [reloadable](../../security/secure-settings.md#reloadable-secure-settings))
 :   A shared access signatures (SAS) token, which the repository’s internal Azure client uses for authentication. The SAS token must have read (r), write (w), list (l), and delete (d) permissions for the repository base path and all its contents. These permissions must be granted for the blob service (b) and apply to resource types service (s), container (c), and object (o). Alternatively, use `key`.
 
 `azure.client.CLIENT_NAME.timeout`

deploy-manage/tools/snapshot-and-restore/google-cloud-storage-repository.md

@@ -123,7 +123,7 @@ bin/elasticsearch-keystore add-file gcs.client.default.credentials_file /path/se
 
 The following are the available client settings. Those that must be stored in the keystore are marked as `Secure`.
 
-`credentials_file` ({{ref}}/secure-settings.html[Secure], [reloadable](../../security/secure-settings.md#reloadable-secure-settings))
+`credentials_file` (https://www.elastic.co/guide/en/elasticsearch/reference/current/secure-settings.html[Secure], [reloadable](../../security/secure-settings.md#reloadable-secure-settings))
 :   The service account file that is used to authenticate to the Google Cloud Storage service.
 
 `endpoint`

deploy-manage/tools/snapshot-and-restore/s3-repository.md

@@ -72,13 +72,13 @@ Define the relevant secure settings in each node’s keystore before starting th
 
 The following list contains the available client settings. Those that must be stored in the keystore are marked as "secure" and are **reloadable**; the other settings belong in the `elasticsearch.yml` file.
 
-`access_key` ({{ref}}/secure-settings.html[Secure], [reloadable](../../security/secure-settings.md#reloadable-secure-settings))
+`access_key` (https://www.elastic.co/guide/en/elasticsearch/reference/current/secure-settings.html[Secure], [reloadable](../../security/secure-settings.md#reloadable-secure-settings))
 :   An S3 access key. If set, the `secret_key` setting must also be specified. If unset, the client will use the instance or container role instead.
 
-`secret_key` ({{ref}}/secure-settings.html[Secure], [reloadable](../../security/secure-settings.md#reloadable-secure-settings))
+`secret_key` (https://www.elastic.co/guide/en/elasticsearch/reference/current/secure-settings.html[Secure], [reloadable](../../security/secure-settings.md#reloadable-secure-settings))
 :   An S3 secret key. If set, the `access_key` setting must also be specified.
 
-`session_token` ({{ref}}/secure-settings.html[Secure], [reloadable](../../security/secure-settings.md#reloadable-secure-settings))
+`session_token` (https://www.elastic.co/guide/en/elasticsearch/reference/current/secure-settings.html[Secure], [reloadable](../../security/secure-settings.md#reloadable-secure-settings))
 :   An S3 session token. If set, the `access_key` and `secret_key` settings must also be specified.
 
 `endpoint`
@@ -96,10 +96,10 @@ The following list contains the available client settings. Those that must be st
 `proxy.scheme`
 :   The scheme to use for the proxy connection to S3. Valid values are either `http` or `https`. Defaults to `http`. This setting allows to specify the protocol used for communication with the proxy server
 
-`proxy.username` ({{ref}}/secure-settings.html[Secure], [reloadable](../../security/secure-settings.md#reloadable-secure-settings))
+`proxy.username` (https://www.elastic.co/guide/en/elasticsearch/reference/current/secure-settings.html[Secure], [reloadable](../../security/secure-settings.md#reloadable-secure-settings))
 :   The username to connect to the `proxy.host` with.
 
-`proxy.password` ({{ref}}/secure-settings.html[Secure], [reloadable](../../security/secure-settings.md#reloadable-secure-settings))
+`proxy.password` (https://www.elastic.co/guide/en/elasticsearch/reference/current/secure-settings.html[Secure], [reloadable](../../security/secure-settings.md#reloadable-secure-settings))
 :   The password to connect to the `proxy.host` with.
 
 `read_timeout`

explore-analyze/machine-learning/nlp/ml-nlp-e5.md

@@ -146,15 +146,15 @@ If you want to install E5 in an air-gapped environment, you have the following o
 
 For the `multilingual-e5-small` model, you need the following files in your system:
 
-```url
+```text
 https://ml-models.elastic.co/multilingual-e5-small.metadata.json
 https://ml-models.elastic.co/multilingual-e5-small.pt
 https://ml-models.elastic.co/multilingual-e5-small.vocab.json
 ```
 
 For the optimized version, you need the following files in your system:
 
-```url
+```text
 https://ml-models.elastic.co/multilingual-e5-small_linux-x86_64.metadata.json
 https://ml-models.elastic.co/multilingual-e5-small_linux-x86_64.pt
 https://ml-models.elastic.co/multilingual-e5-small_linux-x86_64.vocab.json

explore-analyze/machine-learning/nlp/ml-nlp-elser.md

@@ -178,15 +178,15 @@ If you want to deploy ELSER in a restricted or closed network, you have two opti
 
 For the cross-platform verison, you need the following files in your system:
 
-```url
+```text
 https://ml-models.elastic.co/elser_model_2.metadata.json
 https://ml-models.elastic.co/elser_model_2.pt
 https://ml-models.elastic.co/elser_model_2.vocab.json
 ```
 
 For the optimized version, you need the following files in your system:
 
-```url
+```text
 https://ml-models.elastic.co/elser_model_2_linux-x86_64.metadata.json
 https://ml-models.elastic.co/elser_model_2_linux-x86_64.pt
 https://ml-models.elastic.co/elser_model_2_linux-x86_64.vocab.json
@@ -213,7 +213,7 @@ You can use any HTTP service to deploy ELSER. This example uses the official Ngi
 
 4. Verify that Nginx runs properly by visiting the following URL in your browser:
 
-    ```url
+    ```text
     http://{IP_ADDRESS_OR_HOSTNAME}:8080/elser_model_2.metadata.json
     ```
 

explore-analyze/machine-learning/nlp/ml-nlp-rerank.md

@@ -94,7 +94,7 @@ If you want to deploy the Elastic Rerank model in a restricted or closed network
 
 For the cross-platform version, you need the following files in your system:
 
-```url
+```text
 https://ml-models.elastic.co/rerank-v1.metadata.json
 https://ml-models.elastic.co/rerank-v1.pt
 https://ml-models.elastic.co/rerank-v1.vocab.json
@@ -121,7 +121,7 @@ You can use any HTTP service to deploy the model. This example uses the official
 
 4. Verify that Nginx runs properly by visiting the following URL in your browser:
 
-    ```url
+    ```text
     http://{IP_ADDRESS_OR_HOSTNAME}:8080/rerank-v1.metadata.json
     ```
 

get-started/installing-elastic-stack.md

@@ -29,12 +29,12 @@ For more information on supported network configurations, refer to [{{es}} Inges
 
 Install the Elastic Stack products you want to use in the following order:
 
-1. [Elasticsearch]({{ref}}/install-elasticsearch.html)
-2. [Kibana]({{kibana-ref}}/install.html) 
-3. [Logstash]({{logstash-ref}}/installing-logstash.html)
-4. [Elastic Agent]({{fleet-guide}}/elastic-agent-installation.html) or [Beats]({{beats-ref}}/getting-started.html)
-5. [APM]({{apm-guide-ref}}/apm-quick-start.html)
-6. [Elasticsearch Hadoop]({{hadoop-ref}}/install.html)
+1. [Elasticsearch](https://www.elastic.co/guide/en/elasticsearch/reference/current/install-elasticsearch.html)
+2. [Kibana](https://www.elastic.co/guide/en/kibana/current/install.html) 
+3. [Logstash](https://www.elastic.co/guide/en/logstash/current/installing-logstash.html)
+4. [Elastic Agent](https://www.elastic.co/guide/en/fleet/current/elastic-agent-installation.html) or [Beats]({{beats-ref}}/getting-started.html)
+5. [APM](https://www.elastic.co/guide/en/apm/guide/current/apm-quick-start.html)
+6. [Elasticsearch Hadoop](https://www.elastic.co/guide/en/elasticsearch/hadoop/current/install.html)
 
 Installing in this order ensures that the components each product depends on are in place.