Merge branch 'main' into issue-1235-highlighted-fields-serv

nastasha-solomon · web-flow · commit f7ea22c8de08 · 2025-06-04T14:05:12.000-04:00
diff --git a/deploy-manage/deploy/elastic-cloud/create-an-organization.md b/deploy-manage/deploy/elastic-cloud/create-an-organization.md
@@ -76,7 +76,7 @@ During the free 14 day trial, Elastic provides access to one hosted deployment a
 
 * You can have one active deployment at a time
 * The deployment size is limited to 8GB RAM and approximately 360GB of storage, depending on the specified hardware profile
-* Machine learning nodes are available up to 4GB RAM
+* Machine learning nodes are available up to 4GB RAM, or up to 8GB when using Reranker
 * Custom {{es}} plugins are not enabled
 
 For more information, check the [{{ech}} documentation](cloud-hosted.md).
diff --git a/deploy-manage/distributed-architecture/reading-and-writing-documents.md b/deploy-manage/distributed-architecture/reading-and-writing-documents.md
@@ -16,7 +16,7 @@ Each index in {{es}} is [divided into shards](../../deploy-manage/index.md) and
 
 Elasticsearch’s data replication model is based on the *primary-backup model* and is described very well in the [PacificA paper](https://www.microsoft.com/en-us/research/publication/pacifica-replication-in-log-based-distributed-storage-systems/) of Microsoft Research. That model is based on having a single copy from the replication group that acts as the primary shard. The other copies are called *replica shards*. The primary serves as the main entry point for all indexing operations. It is in charge of validating them and making sure they are correct. Once an index operation has been accepted by the primary, the primary is also responsible for replicating the operation to the other copies.
 
-This purpose of this section is to give a high level overview of the {{es}} replication model and discuss the implications it has for various interactions between write and read operations.
+The purpose of this section is to give a high level overview of the {{es}} replication model and discuss the implications it has for various interactions between write and read operations.
 
 ## Basic write model [basic-write-model]
 
diff --git a/deploy-manage/monitor/autoops/ec-autoops-regions.md b/deploy-manage/monitor/autoops/ec-autoops-regions.md
@@ -10,24 +10,36 @@ products:
 
 # AutoOps regions [ec-autoops-regions]
 
-A region is the geographic area where the cloud provider’s data center that hosts your deployments is located. Based on a planned release schedule, Elastic is enabling the AutoOps service on the following cloud service providers: AWS, Azure, and GCP.
+A region is where a cloud service provider's data center that hosts your deployments is located. Based on a planned release schedule, Elastic is enabling AutoOps on the following cloud service providers: AWS, Azure, and GCP.
 
-AutoOps is currently available in the following regions:
+AutoOps is currently available in the following regions for AWS:
 
-| Provider | Region | Name |
+| Region | Name |
 | --- | --- | --- | --- |
-| AWS | us-east-1 | US East (N. Virginia) |
-| AWS | us-east-2 | Ohio | 
-| AWS | us-west-2 | Oregon |
-| AWS | eu-west-1 | Ireland |
-| AWS | eu-west-2 | London |
-| AWS | eu-central-1 | Frankfurt |
-| AWS | ap-southeast-1 | Singapore |
-| AWS | ap-northeast-1| Tokyo | 
-| AWS | ap-south-1 | Mumbai | 
+| us-east-1 | N. Virginia |
+| us-east-2 | Ohio |
+| us-west-1 | N. California |
+| us-west-2 | Oregon |
+| ca-central-1 | Canada |
+| eu-west-1 | Ireland |
+| eu-west-2 | London |
+| eu-west-3 | Paris |
+| eu-north-1 | Stockholm |
+| eu-central-1 | Frankfurt |
+| eu-central-2 | Zurich |
+| eu-south-1 | Milan |
+| me-south-1 | Bahrain |
+| ap-east-1 | Hong Kong |
+| ap-northeast-1 | Tokyo |
+| ap-northeast-2 | Seoul |
+| ap-southeast-1 | Singapore |
+| ap-southeast-2 | Sydney |
+| ap-south-1 | Mumbai |
+| sa-east-1 | Sao Paulo |
+| af-south-1 | Cape Town |
+
+Regions for Azure and GCP will be added in the future.
 
 ::::{note} 
-Currently, a limited number of AWS regions are available. More regions for AWS, Azure and GCP will be added in the future. Also, AutoOps is currently not available for GovCloud customers.
+AutoOps is currently not available for GovCloud customers.
 ::::
-
-
diff --git a/deploy-manage/remote-clusters/ec-remote-cluster-same-ess.md b/deploy-manage/remote-clusters/ec-remote-cluster-same-ess.md
@@ -52,9 +52,9 @@ If you run into any issues, refer to [Troubleshooting](/troubleshoot/elasticsear
 * Copy the encoded key (`encoded` in the response) to a safe location. You will need it in the next step.
 
 
-### Add the cross-cluster API key to the keystore of the local deployment [ec_add_the_cross_cluster_api_key_to_the_keystore_of_the_local_deployment]
+### Add the cross-cluster API key to the local deployment [ec_add_the_cross_cluster_api_key_to_the_local_deployment]
 
-The API key created previously will be used by the local deployment to authenticate with the corresponding set of permissions to the remote deployment. For that, you need to add the API key to the local deployment’s keystore.
+The API key created previously will be used by the local deployment to authenticate with the corresponding set of permissions to the remote deployment. For that, you need to add the API key to the local deployment.
 
 1. Log in to the [{{ecloud}} Console](https://cloud.elastic.co?page=docs&placement=docs-body).
 2. On the home page, find your hosted deployment and select **Manage** to access it directly. Or, select **Hosted deployments** to go to the **Hosted deployments** page to view all of your deployments.
@@ -69,12 +69,12 @@ The API key created previously will be used by the local deployment to authentic
         * For the **Setting name**, enter the the alias of your choice. You will use this alias to connect to the remote cluster later. It must be lowercase and only contain letters, numbers, dashes and underscores.
         * For the **Secret**, paste the encoded cross-cluster API key.
 
-    2. Click **Add** to save the API key to the keystore.
+    2. Click **Add** to save the API key.
 
-5. Restart the local deployment to reload the keystore with its new setting. To do that, go to the deployment’s main page (named after your deployment’s name), locate the **Actions** menu, and select **Restart {{es}}**.<br>
+5. Restart the local deployment to reload the new setting. To do that, go to the deployment’s main page (named after your deployment’s name), locate the **Actions** menu, and select **Restart {{es}}**.<br>
 
     ::::{note}
-    If the local deployment runs on version 8.14 or greater, you no longer need to perform this step because the keystore is reloaded automatically with the new API keys.
+    If the local deployment runs on version 8.14 or greater, you no longer need to perform this step.
     ::::
 
 
diff --git a/deploy-manage/upgrade/prepare-to-upgrade.md b/deploy-manage/upgrade/prepare-to-upgrade.md
@@ -19,7 +19,9 @@ Upgrading from a release candidate build, such as 9.0.0-rc1, is unsupported. Use
 
 To upgrade from 8.17.0 or earlier to 9.0.0, you must first upgrade to the latest 8.18 patch release. This allows you to use the [Upgrade Assistant](prepare-to-upgrade/upgrade-assistant.md) to identify and resolve issues, reindex indices created before 8.0.0, and perform a rolling upgrade. Upgrading to the latest 8.18 patch release is required even if you choose a full {{es}} cluster restart. If you're using 7.x and earlier, you may need to complete multiple upgrades or perform a full-cluster restart to reach the latest 8.18 patch release before upgrading to 9.0.0.
 
-Alternatively, you can create a 9.0.0 deployment and reindex from remote. For more information, refer to [Reindex to upgrade](#reindex-to-upgrade).
+If you are already running an 8.18.x version, it's also recommended to upgrade to the latest 8.18 patch release before upgrading to 9.x. This ensures that the latest version of the upgrade assistant is used, and any bug fixes that could have implications for the upgrade are applied.
+
+As an alternative to upgrading the cluster, you can create a new 9.0.0 deployment and reindex from the original cluster. For more information, refer to [Reindex to upgrade](#reindex-to-upgrade).
 
 :::{note}
 For flexible upgrade scheduling, 8.18.0 {{beats}} and {{ls}} are compatible with 9.x {{es}}.
diff --git a/reference/fleet/remote-elasticsearch-output.md b/reference/fleet/remote-elasticsearch-output.md
@@ -13,11 +13,15 @@ Remote {{es}} outputs allow you to send {{agent}} data to a remote {{es}} cluste
 A remote {{es}} cluster supports the same [output settings](/reference/fleet/es-output-settings.md) as your main {{es}} cluster.
 
 ::::{note}
-Note the following restrictions with the remote {es} output:
+This feature is part of the Enterprise subscription offering under the name of **Per Integration output assignment**. Refer to [Subscriptions](https://www.elastic.co/subscriptions) for more information.
+::::
+
+## Limitations
+
+These limitations apply to remote {{es}} output:
 
 * Using a remote {{es}} output with a target cluster that has [traffic filters](/deploy-manage/security/traffic-filtering.md) enabled is not currently supported.
 * Using {{elastic-defend}} is currently not supported when a remote {{es}} output is configured for an agent.
-::::
 
 ## Configuration
 
diff --git a/release-notes/fleet-elastic-agent/known-issues.md b/release-notes/fleet-elastic-agent/known-issues.md
@@ -12,11 +12,37 @@ Known issues are significant defects or limitations that may impact your impleme
 % On [Month Day, Year], a known issue was discovered that [description of known issue].
 % For more information, check [Issue #](Issue link).
 
-% **Workaround** 
+% **Workaround**
 % Workaround description.
 
 % :::
 
+:::{dropdown} [Windows] {{agent}} is unable to re-enroll into {{fleet}}
+
+**Applies to: {{agent}} 9.0.0, 9.0.1, 9.0.2 (Windows only)**
+
+On April 9, 2025, a known issue was discovered where an {{agent}} installed on Windows and previously enrolled into {{fleet}} is unable to re-enroll. Attempting to enroll the {{agent}} fails with the following error:
+
+```shell
+Error: the command is executed as root but the program files are not owned by the root user.
+```
+
+For more information, check [Issue #7794](https://github.com/elastic/elastic-agent/issues/7794).
+
+**Workaround**
+
+Until a bug fix is available in a later release, you can resolve the issue temporarily using the following workaround:
+
+1. Change the ownership of the {{agent}} directory:
+
+  ```shell
+  icacls "C:\Program Files\Elastic\Agent" /setowner "NT AUTHORITY\SYSTEM" /t /l
+  ```
+
+2. After the output confirms all files were successfully processed, run the `enroll` command again.
+
+:::
+
 :::{dropdown} [macOS] Osquery integration fails to start on fresh agent installs
 
 **Applies to: {{agent}} 9.0.0 and 9.0.1 (macOS only)**
@@ -25,7 +51,7 @@ On May 26th, 2025, a known issue was discovered that causes the `osquery` integr
 
 For more information, check [Issue #8245](https://github.com/elastic/elastic-agent/issues/8245).
 
-**Workaround** 
+**Workaround**
 
 As a workaround, you can manually restore the `osquery.app/` directory as follows:
 
diff --git a/solutions/security/cloud/cloud-security-posture-management.md b/solutions/security/cloud/cloud-security-posture-management.md
@@ -21,7 +21,7 @@ This feature currently supports agentless and agent-based deployments on Amazon
 * Minimum privileges vary depending on whether you need to read, write, or manage CSPM data and integrations. Refer to [CSPM privilege requirements](/solutions/security/cloud/cspm-privilege-requirements.md).
 * The CSPM integration is available to all {{ecloud}} users. On-premise deployments require an [Enterprise subscription](https://www.elastic.co/pricing).
 * CSPM only works in the `Default` {{kib}} space. Installing the CSPM integration on a different {{kib}} space will not work.
-* CSPM is supported only on AWS, GCP, and Azure commercial cloud platforms, and AWS GovCloud. Other government cloud platforms are not supported. [Click here to request support](https://github.com/elastic/kibana/issues/new/choose).
+* CSPM supports only the AWS, GCP, and Azure commercial cloud platforms, and AWS GovCloud. AWS GovCloud is only supported for agent-based deployments — agentless deployments do not work on this platform. Other government cloud platforms are not supported. To request support for other platforms, [open a GitHub issue](https://github.com/elastic/kibana/issues/new/choose).
 
 ::::
 
diff --git a/solutions/security/cloud/get-started-with-cspm-for-aws.md b/solutions/security/cloud/get-started-with-cspm-for-aws.md
@@ -21,7 +21,7 @@ This page explains how to get started monitoring the security posture of your cl
 * Minimum privileges vary depending on whether you need to read, write, or manage CSPM data and integrations. Refer to [CSPM privilege requirements](/solutions/security/cloud/cspm-privilege-requirements.md).
 * The CSPM integration is available to all {{ecloud}} users. On-premise deployments require an [Enterprise subscription](https://www.elastic.co/pricing).
 * CSPM only works in the `Default` {{kib}} space. Installing the CSPM integration on a different {{kib}} space will not work.
-* CSPM is supported only on AWS, GCP, and Azure commercial cloud platforms, and AWS GovCloud. Other government cloud platforms are not supported. [Click here to request support](https://github.com/elastic/kibana/issues/new/choose).
+* CSPM supports only the AWS, GCP, and Azure commercial cloud platforms, and AWS GovCloud. AWS GovCloud is only supported for agent-based deployments — agentless deployments do not work on this platform. Other government cloud platforms are not supported. To request support for other platforms, [open a GitHub issue](https://github.com/elastic/kibana/issues/new/choose).
 * The user who gives the CSPM integration AWS permissions must be an AWS account `admin`.
 
 ::::
