Merge branch 'main' into 2025/10/16/s3-replication

Author: DaveCTurner

deploy-manage/deploy/elastic-cloud/serverless.md

@@ -65,6 +65,8 @@ To learn more about serverless status, see [Service status](../../cloud-organiza
 
 The following FAQ addresses common questions about using {{serverless-full}} projects.
 
+For information about upcoming features, refer to our [roadmap](https://www.elastic.co/cloud/serverless/roadmap).
+
 ### Pricing and availability
 **Q: Where can I learn about pricing for {{serverless-short}}?**  
 A: See pricing information for [{{es-serverless}}](https://www.elastic.co/pricing/serverless-search), [{{observability}}](https://www.elastic.co/pricing/serverless-observability), and [{{sec-serverless}}](https://www.elastic.co/pricing/serverless-security).
@@ -73,6 +75,7 @@ A: See pricing information for [{{es-serverless}}](https://www.elastic.co/pricin
 A: {{serverless-full}} is available in select AWS, GCP, and Azure regions, with plans to expand to more regions. For more information, refer to [](/deploy-manage/deploy/elastic-cloud/regions.md).
 
 ### Data management
+
 **Q: How can I move data to or from {{serverless-short}} projects?**  
 A: We are working on data migration tools. In the interim, [use Logstash](logstash://reference/index.md) with {{es}} input and output plugins to move data to and from {{serverless-short}} projects.
 
@@ -83,6 +86,9 @@ A: Request for project backups or restores is currently unsupported, and we are
 **Q: How can I create {{serverless-full}} service accounts?**  
 A: Create API keys for service accounts in your {{serverless-short}} projects. Options to automate the creation of API keys with tools such as Terraform will be available in the future.
 
+**Q: What compliance and privacy standards does {{serverless-full}} adhere to?**  
+A: Alongside the entire Elastic platform, {{serverless-full}} is independently audited and certified to meet industry-leading compliance and privacy standards. Refer to the [Elastic Trust Center](https://www.elastic.co/trust) for more information. Further details about specific standards are available on our [roadmap](https://www.elastic.co/cloud/serverless/roadmap).
+
 ### Project lifecycle and support
 **Q: How does {{serverless-full}} ensure compatibility between software versions?**  
 A: Connections and configurations are unaffected by upgrades. To ensure compatibility between software versions, quality testing and API versioning are used.

deploy-manage/remote-clusters/remote-clusters-self-managed.md

@@ -35,21 +35,21 @@ $$$sniff-mode$$$
 Sniff mode
 :   In sniff mode, a cluster alias is registered with a name of your choosing and a list of addresses of *seed* nodes specified with the `cluster.remote.<cluster_alias>.seeds` setting. When you register a remote cluster using sniff mode, {{es}} retrieves from one of the seed nodes the addresses of up to three *gateway nodes*. Each `remote_cluster_client` node in the local {{es}} cluster then opens several TCP connections to the publish addresses of the gateway nodes. This mode therefore requires that the gateway nodes' publish addresses are accessible to nodes in the local cluster.
 
-    Sniff mode is the default connection mode. See [Sniff mode remote cluster settings](remote-clusters-settings.md#remote-cluster-sniff-settings) for more information about configuring sniff mode.
+    Sniff mode is the default connection mode. See [Sniff mode remote cluster settings](elasticsearch://reference/elasticsearch/configuration-reference/remote-clusters.md#remote-cluster-sniff-settings) for more information about configuring sniff mode.
 
     $$$gateway-nodes-selection$$$
     The *gateway nodes* selection depends on the following criteria:
 
     * **version**: Remote nodes must be compatible with the cluster they are registered to.
     * **role**: By default, any non-[master-eligible](/deploy-manage/distributed-architecture/clusters-nodes-shards/node-roles.md#master-node-role) node can act as a gateway node. Dedicated master nodes are never selected as gateway nodes.
-    * **attributes**: You can define the gateway nodes for a cluster by setting [`cluster.remote.node.attr.gateway`](remote-clusters-settings.md#cluster-remote-node-attr) to `true`. However, such nodes still have to satisfy the two above requirements.
+    * **attributes**: You can define the gateway nodes for a cluster by setting [`cluster.remote.node.attr.gateway`](elasticsearch://reference/elasticsearch/configuration-reference/remote-clusters.md#cluster-remote-node-attr) to `true`. However, such nodes still have to satisfy the two above requirements.
 
 
 $$$proxy-mode$$$
 
 Proxy mode
 :   In proxy mode, a cluster alias is registered with a name of your choosing and the address of a TCP (layer 4) reverse proxy specified with the `cluster.remote.<cluster_alias>.proxy_address` setting. You must configure this proxy to route connections to one or more nodes of the remote cluster. When you register a remote cluster using proxy mode, {{es}} opens several TCP connections to the proxy address and uses these connections to communicate with the remote cluster. In proxy mode {{es}} disregards the publish addresses of the remote cluster nodes which means that the publish addresses of the remote cluster nodes need not be accessible to the local cluster.
 
-    Proxy mode is not the default connection mode, so you must set `cluster.remote.<cluster_alias>.mode: proxy` to use it. See [Proxy mode remote cluster settings](remote-clusters-settings.md#remote-cluster-proxy-settings) for more information about configuring proxy mode.
+    Proxy mode is not the default connection mode, so you must set `cluster.remote.<cluster_alias>.mode: proxy` to use it. See [Proxy mode remote cluster settings](elasticsearch://reference/elasticsearch/configuration-reference/remote-clusters.md#remote-cluster-proxy-settings) for more information about configuring proxy mode.
 
     Proxy mode has the same [version compatibility requirements](#gateway-nodes-selection) as sniff mode.

deploy-manage/remote-clusters/remote-clusters-settings.md

@@ -656,7 +656,6 @@ toc:
           - file: remote-clusters/remote-clusters-api-key.md
           - file: remote-clusters/remote-clusters-cert.md
           - file: remote-clusters/remote-clusters-migrate.md
-          - file: remote-clusters/remote-clusters-settings.md
       - file: remote-clusters/eck-remote-clusters.md
   - file: monitor.md
     children:

deploy-manage/toc.yml

@@ -45,18 +45,20 @@ The panels you create using the following editors support dashboard drilldowns:
 Use the [**Sample web logs**](../index.md#gs-get-data-into-kibana) data to create a dashboard and add panels, then set a search and filter on the **[Logs] Web Traffic** dashboard.
 
 1. Add the **Sample web logs** data.
-2. Create a new dashboard, click **Add from Library**, then add the following panels:
+2. Create a new dashboard.
 
-    * **[Logs] Response Codes Over Time + Annotations**
-    * **[Logs] Visits**
+    * {applies_to}`stack: ga 9.2` Select **Add** > **From library** in the toolbar.
+    * {applies_to}`stack: ga 9.0` Click **Add from library** in the dashboard toolbar.
 
-3. Set the [time filter](../query-filter/filtering.md) to **Last 30 days**.
-4. Save the dashboard. In the **Title** field, enter `Detailed logs`.
-5. Open the **[Logs] Web Traffic** dashboard, then set a search and filter.
+3. Add the following panel:
 
-    Search: `extension.keyword: ("gz" or "css" or "deb")`<br> Filter: `geo.src: US`
+    * **[Logs] Visits**
 
+4. Set the [time filter](../query-filter/filtering.md) to **Last 30 days**.
+5. Save the dashboard. In the **Title** field, enter `Detailed logs`.
+6. Open the **[Logs] Web Traffic** dashboard, then set a search and filter.
 
+    Search: `extension.keyword: ("gz" or "css" or "deb")`<br> Filter: `geo.src: US`
 
 ### Create the dashboard drilldown [_create_the_dashboard_drilldown]
 
@@ -77,8 +79,6 @@ Create a drilldown that opens the **Detailed logs** dashboard from the **[Logs]
    :screenshot:
    :::
 
-
-
 ## Create URL drilldowns [create-url-drilldowns]
 
 URL drilldowns enable you to navigate from a dashboard to external websites. Destination URLs can be dynamic, depending on the dashboard context or user interaction with a panel. To create URL drilldowns, you add [variables](/explore-analyze/dashboards/drilldowns.md) to a URL template, which configures the behavior of the drilldown. All panels that you create with the visualization editors support dashboard drilldowns.
@@ -92,22 +92,23 @@ Some panels support multiple interactions, also known as triggers. The [variable
 
 For example, **Single click** has `{{event.value}}` and **Range selection** has `{{event.from}}` and `{{event.to}}`.
 
-
 ### Create a URL drilldown [_create_a_url_drilldown]
 
 For example, if you have a dashboard that shows data from a Github repository, you can create a URL drilldown that opens Github from the dashboard panel.
 
 1. Add the [**Sample web logs**](../index.md#gs-get-data-into-kibana) data.
 2. Open the **[Logs] Web Traffic** dashboard.
 3. In the toolbar, click **Edit**.
-4. Create a donut chart
+4. Create a pie chart.
+
+    * {applies_to}`stack: ga 9.2` Select **Add** > **Visualization** in the toolbar.
+    * {applies_to}`stack: ga 9.0` Click **Create visualization** in the dashboard toolbar.
 
-    1. Click **Create visualization**.
-    2. From the **Chart type** dropdown, select **Donut**.
-    3. From the **Available fields** list, drag **machine.os.keyword** to the workspace.
-    4. Click **Save and return**.
+2. From the **Chart type** dropdown, select **Pie**.
+3. From the **Available fields** list, drag **machine.os.keyword** to the workspace.
+4. Click **Save and return**.
 
-5. Open the donut chart panel menu, then select **Create drilldown**.
+5. Open the pie chart panel menu, then select **Create drilldown**.
 6. Click **Go to URL**.
 
     1. Give the drilldown a name. For example, `Show on Github`.
@@ -123,7 +124,7 @@ For example, if you have a dashboard that shows data from a Github repository, y
     4. Click **Create drilldown**.
 
 7. Save the dashboard.
-8. On the donut chart panel, click any chart slice, then select **Show on Github**.
+8. On the pie chart panel, click any chart slice, then select **Show on Github**.
 
     ![URL drilldown popup](/explore-analyze/images/kibana-dashboard_urlDrilldownPopup_8.3.png "")