Merge branch 'main' into fundamentals-fix

jmikell821 · web-flow · commit 99614ad4a8d7 · 2025-10-31T14:26:52.000-04:00
diff --git a/deploy-manage/deploy/_snippets/ece-fips-message.md b/deploy-manage/deploy/_snippets/ece-fips-message.md
@@ -0,0 +1 @@
+FIPS (Federal Information Processing Standards) compliance is not officially supported in ECE. While ECE may function on FIPS-enabled systems, this configuration has not been validated through our testing processes and is not recommended for production environments.
diff --git a/deploy-manage/deploy/_snippets/ece-supported-combinations.md b/deploy-manage/deploy/_snippets/ece-supported-combinations.md
@@ -0,0 +1,6 @@
+::::{important}
+Make sure to use a supported combination of Linux distribution and container engine version as defined in our official [Support matrix](https://www.elastic.co/support/matrix#elastic-cloud-enterprise). Unsupported combinations can lead to various issues in your ECE environment, including failures when creating system deployments, upgrading workload deployments, proxy timeouts, and more.
+
+:::{include} /deploy-manage/deploy/_snippets/ece-fips-message.md
+:::
+::::
diff --git a/deploy-manage/deploy/cloud-enterprise/configure-host-rhel.md b/deploy-manage/deploy/cloud-enterprise/configure-host-rhel.md
@@ -25,8 +25,7 @@ Verify that required traffic is allowed. Check the [Networking prerequisites](ec
 
 **Example:** For AWS, allowing traffic between hosts is implemented using security groups.
 
-::::{important}
-Make sure to use a supported combination of Linux distribution and container engine version as defined in our official [Support matrix](https://www.elastic.co/support/matrix#elastic-cloud-enterprise). Unsupported combinations can lead to various issues in your ECE environment, including failures when creating system deployments, upgrading workload deployments, proxy timeouts, and more.
+::::{include} /deploy-manage/deploy/_snippets/ece-supported-combinations.md
 ::::
 
 ## Install Podman and configure the host [ece-configure-hosts-rhel8-podman]
diff --git a/deploy-manage/deploy/cloud-enterprise/configure-host-suse.md b/deploy-manage/deploy/cloud-enterprise/configure-host-suse.md
@@ -28,8 +28,7 @@ Regardless of which approach you take, the steps in this section need to be perf
 
 ## Install Docker on SLES [ece-install-docker-sles12]
 
-::::{important}
-Make sure to use a supported combination of Linux distribution and container engine version as defined in our official [Support matrix](https://www.elastic.co/support/matrix#elastic-cloud-enterprise). Unsupported combinations can lead to various issues in your ECE environment, including failures when creating system deployments, upgrading workload deployments, proxy timeouts, and more.
+::::{include} /deploy-manage/deploy/_snippets/ece-supported-combinations.md
 ::::
 
 
diff --git a/deploy-manage/deploy/cloud-enterprise/configure-host-ubuntu.md b/deploy-manage/deploy/cloud-enterprise/configure-host-ubuntu.md
@@ -24,8 +24,7 @@ The following instructions show you how to prepare your hosts on Ubuntu.
 
 Install a compatible Docker version on Ubuntu.
 
-::::{important}
-Make sure to use a supported combination of Linux distribution and container engine version as defined in our official [Support matrix](https://www.elastic.co/support/matrix#elastic-cloud-enterprise). Unsupported combinations can lead to various issues in your ECE environment, including failures when creating system deployments, upgrading workload deployments, proxy timeouts, and more.
+::::{include} /deploy-manage/deploy/_snippets/ece-supported-combinations.md
 ::::
 
 
diff --git a/deploy-manage/deploy/cloud-enterprise/configure-operating-system.md b/deploy-manage/deploy/cloud-enterprise/configure-operating-system.md
@@ -17,6 +17,5 @@ Before installing {{ece}}, you have to prepare your hosts with one of the follow
 * [Red Hat Enterprise Linux (RHEL) and Rocky Linux](configure-host-rhel.md)
 * [SUSE Linux Enterprise Server (SLES)](configure-host-suse.md)
 
-::::{important}
-Make sure to use a supported combination of Linux distribution and container engine version, such as `Docker` or `Podman`, as defined in our official [Support matrix](https://www.elastic.co/support/matrix#elastic-cloud-enterprise). Unsupported combinations can lead to various issues in your ECE environment, including failures when creating system deployments, upgrading workload deployments, proxy timeouts, and more.
-::::
+::::{include} /deploy-manage/deploy/_snippets/ece-supported-combinations.md
+::::
diff --git a/deploy-manage/deploy/cloud-enterprise/default-system-deployment-versions.md b/deploy-manage/deploy/cloud-enterprise/default-system-deployment-versions.md
@@ -16,9 +16,11 @@ Note that since version 2.7.0, system deployments are automatically upgraded whe
 
 | {{ece}} version | Admin cluster | Logging & Metrics cluster | Security cluster |
 | --- | --- | --- | --- |
+| 4.0.3 | 8.18.8 | 8.18.8 | 8.18.8 |
 | 4.0.2 | 8.18.8 | 8.18.8 | 8.18.8 |
 | 4.0.1 | 8.18.2 | 8.18.2 | 8.18.2 |
 | 4.0.0 | 8.18.0 | 8.18.0 | 8.18.0 |
+| 3.8.3 | 8.17.10 | 8.17.10 | 8.17.10 |
 | 3.8.2 | 8.17.10 | 8.17.10 | 8.17.10 |
 | 3.8.1 | 8.17.4 | 8.17.4 | 8.17.4 |
 | 3.8.0 | 8.17.4 | 8.17.4 | 8.17.4 |
diff --git a/deploy-manage/deploy/cloud-enterprise/ece-install-offline-no-registry.md b/deploy-manage/deploy/cloud-enterprise/ece-install-offline-no-registry.md
@@ -36,13 +36,13 @@ To perform an offline installation without a private Docker registry, you have t
 
     ```sh subs=true
     docker save -o ece.{{version.ece}}.tar docker.elastic.co/cloud-enterprise/elastic-cloud-enterprise:{{version.ece}}
-    docker save -o es.8.18.2.tar docker.elastic.co/cloud-release/elasticsearch-cloud-ess:{{ece-docker-images-8}}
-    docker save -o kibana.8.18.2.tar docker.elastic.co/cloud-release/kibana-cloud:{{ece-docker-images-8}}
-    docker save -o apm.8.18.2.tar docker.elastic.co/cloud-release/elastic-agent-cloud:{{ece-docker-images-8}}
-    docker save -o enterprise-search.8.18.2.tar docker.elastic.co/cloud-release/enterprise-search-cloud:{{ece-docker-images-8}}
-    docker save -o es.9.0.1.tar docker.elastic.co/cloud-release/elasticsearch-cloud-ess:{{ece-docker-images-9}}
-    docker save -o kibana.9.0.1.tar docker.elastic.co/cloud-release/kibana-cloud:{{ece-docker-images-9}}
-    docker save -o apm.9.0.1.tar docker.elastic.co/cloud-release/elastic-agent-cloud:{{ece-docker-images-9}}
+    docker save -o es.{{ece-docker-images-8}}.tar docker.elastic.co/cloud-release/elasticsearch-cloud-ess:{{ece-docker-images-8}}
+    docker save -o kibana.{{ece-docker-images-8}}.tar docker.elastic.co/cloud-release/kibana-cloud:{{ece-docker-images-8}}
+    docker save -o apm.{{ece-docker-images-8}}.tar docker.elastic.co/cloud-release/elastic-agent-cloud:{{ece-docker-images-8}}
+    docker save -o enterprise-search.{{ece-docker-images-8}}.tar docker.elastic.co/cloud-release/enterprise-search-cloud:{{ece-docker-images-8}}
+    docker save -o es.{{ece-docker-images-9}}.tar docker.elastic.co/cloud-release/elasticsearch-cloud-ess:{{ece-docker-images-9}}
+    docker save -o kibana.{{ece-docker-images-9}}.tar docker.elastic.co/cloud-release/kibana-cloud:{{ece-docker-images-9}}
+    docker save -o apm.{{ece-docker-images-9}}.tar docker.elastic.co/cloud-release/elastic-agent-cloud:{{ece-docker-images-9}}
     ```
 
 3. Copy the .tar files to a location on your network where they are available to each host where you plan to install {{ece}}. Alternatively, you can copy the .tar files to each host directly.
diff --git a/deploy-manage/deploy/cloud-enterprise/ece-install-offline-with-registry.md b/deploy-manage/deploy/cloud-enterprise/ece-install-offline-with-registry.md
@@ -42,13 +42,13 @@ Installing ECE on multiple hosts with your own registry server is simpler, becau
 
     ```sh subs=true
     docker tag docker.elastic.co/cloud-enterprise/elastic-cloud-enterprise:{{version.ece}} REGISTRY/cloud-enterprise/elastic-cloud-enterprise:{{version.ece}}
-    docker tag docker.elastic.co/cloud-release/elasticsearch-cloud-ess:8.18.2 REGISTRY/cloud-release/elasticsearch-cloud-ess:{{ece-docker-images-8}}
-    docker tag docker.elastic.co/cloud-release/kibana-cloud:8.18.2 REGISTRY/cloud-release/kibana-cloud:{{ece-docker-images-8}}
-    docker tag docker.elastic.co/cloud-release/elastic-agent-cloud:8.18.2 REGISTRY/cloud-release/elastic-agent-cloud:{{ece-docker-images-8}}
-    docker tag docker.elastic.co/cloud-release/enterprise-search-cloud:8.18.2 REGISTRY/cloud-release/enterprise-search-cloud:{{ece-docker-images-8}}
-    docker tag docker.elastic.co/cloud-release/elasticsearch-cloud-ess:9.0.1 REGISTRY/cloud-release/elasticsearch-cloud-ess:{{ece-docker-images-9}}
-    docker tag docker.elastic.co/cloud-release/kibana-cloud:9.0.1 REGISTRY/cloud-release/kibana-cloud:{{ece-docker-images-9}}
-    docker tag docker.elastic.co/cloud-release/elastic-agent-cloud:9.0.1 REGISTRY/cloud-release/elastic-agent-cloud:{{ece-docker-images-9}}
+    docker tag docker.elastic.co/cloud-release/elasticsearch-cloud-ess:{{ece-docker-images-8}} REGISTRY/cloud-release/elasticsearch-cloud-ess:{{ece-docker-images-8}}
+    docker tag docker.elastic.co/cloud-release/kibana-cloud:{{ece-docker-images-8}} REGISTRY/cloud-release/kibana-cloud:{{ece-docker-images-8}}
+    docker tag docker.elastic.co/cloud-release/elastic-agent-cloud:{{ece-docker-images-8}} REGISTRY/cloud-release/elastic-agent-cloud:{{ece-docker-images-8}}
+    docker tag docker.elastic.co/cloud-release/enterprise-search-cloud:{{ece-docker-images-8}} REGISTRY/cloud-release/enterprise-search-cloud:{{ece-docker-images-8}}
+    docker tag docker.elastic.co/cloud-release/elasticsearch-cloud-ess:{{ece-docker-images-9}} REGISTRY/cloud-release/elasticsearch-cloud-ess:{{ece-docker-images-9}}
+    docker tag docker.elastic.co/cloud-release/kibana-cloud:{{ece-docker-images-9}} REGISTRY/cloud-release/kibana-cloud:{{ece-docker-images-9}}
+    docker tag docker.elastic.co/cloud-release/elastic-agent-cloud:{{ece-docker-images-9}} REGISTRY/cloud-release/elastic-agent-cloud:{{ece-docker-images-9}}
     ```
 
 4. Push the Docker images to your private Docker registry, using the same tags from the previous step. Replace `REGISTRY` with your actual registry URL, for example `my.private.repo:5000`:
diff --git a/deploy-manage/deploy/cloud-enterprise/ece-software-prereq.md b/deploy-manage/deploy/cloud-enterprise/ece-software-prereq.md
@@ -16,6 +16,7 @@ To install ECE, make sure you prepare your environment with the following softwa
 * [Linux distributions with compatible Docker versions](#ece-linux-docker)
 * [Free RAM](#ece-free-ram)
 * [XFS](#ece-xfs)
+* [FIPS compliance](#ece-fips)
 
 
 ## Supported Linux kernel [ece-linux-kernel] 
@@ -81,3 +82,9 @@ You must use XFS and have quotas enabled on all allocators, otherwise disk usage
 ::::
 
 
+## FIPS compliance [ece-fips]
+
+:::{include} /deploy-manage/deploy/_snippets/ece-fips-message.md
+:::
+
+For more information about FIPS compliance across the {{stack}}, refer to [](/deploy-manage/security/fips.md).
diff --git a/deploy-manage/deploy/cloud-enterprise/install.md b/deploy-manage/deploy/cloud-enterprise/install.md
@@ -17,6 +17,10 @@ products:
 
 You can deploy {{ece}} (ECE) on public or private clouds, virtual machines, or on-premises.
 
+::::{tip}
+If you already have an ECE platform up and running, and you want to add hosts to your installation, refer to [](./install-ece-on-additional-hosts.md).
+::::
+
 In ECE, a host refers to any server, VM, or cloud instance where the ECE software is installed. An ECE platform consists of multiple hosts working together to orchestrate {{stack}} applications.
 
 For public cloud deployments, you can choose from the following providers:
@@ -25,10 +29,6 @@ For public cloud deployments, you can choose from the following providers:
 * Google Cloud Platform (GCP)
 * Microsoft Azure
 
-::::{tip}
-If you already have an ECE platform up and running, and you want to add hosts to your installation, refer to [](./install-ece-on-additional-hosts.md).
-::::
-
 ::::{note}
 In these pages we frequently refer to [Docker](https://www.docker.com/), as its currently the most common container engine, but these instructions are generally valid for [Podman](https://podman.io/) as well, with `podman` replacing `docker` in commands as appropriate.
 ::::
@@ -41,6 +41,9 @@ Before you start, make sure to [identify your deployment scenario](identify-depl
 
 After completing the prerequisites, proceed to configure your ECE hosts. This includes installing Docker or Podman, setting up XFS quotas, preparing mount points, and other required configurations.
 
+::::{include} /deploy-manage/deploy/_snippets/ece-supported-combinations.md
+::::
+
 ECE supports a [wide range of OS versions](https://www.elastic.co/support/matrix#elastic-cloud-enterprise). Below are some OS-specific instructions for preparing your hosts, though other versions follow a similar process. Choose the appropriate guide for your operating system and follow the instructions:
 
 * [Ubuntu 20.04 LTS (Focal Fossa) and Ubuntu 22.04 LTS (Jammy Jellyfish)](configure-host-ubuntu.md)
diff --git a/deploy-manage/deploy/elastic-cloud/azure-marketplace-pricing.md b/deploy-manage/deploy/elastic-cloud/azure-marketplace-pricing.md
@@ -4,7 +4,7 @@ mapped_pages:
 applies_to:
   deployment:
     ess: ga
-  serverless: preview
+  serverless: ga
 products:
   - id: cloud-hosted
 ---
@@ -13,17 +13,30 @@ products:
 
 The pricing in Azure Marketplace defines how on-demand usage and prepaid fees get converted from ECUs and discounts into the local currency in which you transact on Azure Marketplace.
 
-We will be updating the pricing plan for {{ecloud}} on Azure Marketplace effective January 1st, 2024. This update will affect customers paying in non-USD currencies.
-
+We will be updating the pricing plan for {{ecloud}} on Azure Marketplace effective November 1st, 2025. This update will affect customers paying in CHF, DKK, EUR, GBP, or SEK.
+In the past, we had updated the pricing plan for {{ecloud}} on Azure Marketplace effective January 1st, 2024. This update had affected customers paying in non-USD currencies.
 
 ## Why we’re making these changes [ec_why_were_making_these_changes]
 
 The pricing plan update enables us to align with market trends and adapt to changing economic conditions, ensuring that we continue delivering the highest standard of service.
 
+## Who is affected in November 2025 [ec_who_is_affected-nov-2025]
+
+These price changes will apply to customers who are currently paying for Azure Marketplace services CHF, DKK, EUR, GBP, or SEK. If you are paying in USD or any other currency, your pricing and billing will remain unchanged.
+Note that if you are using a private plan, your price is not affected.
+
+| Currency | Price | Elastic Billing Units for Azure† |
+| --- | --- | --- |
+| CHF | 0.9 | CHF 0.09 per 1000 units |
+| DKK | 7.1 | 0.74 kr. per 1000 units |
+| EUR | 0.9 | €0.09 per 1000 units |
+| GBP | 0.8 | £0.08 per 1000 units |
+| SEK | 10.6 | 1,06 kr. per 1000 units |
+| TWD | 32.7 | NT$3.27 per 1000 units |
 
-## Who is affected [ec_who_is_affected]
+## Who was affected in January 2024 [ec_who_is_affected]
 
-These pricing changes will apply to customers who are currently paying for Azure Marketplace services in non-USD currencies. If you are paying in USD, your pricing and billing will remain unchanged.
+These pricing changes have applied to customers who were currently paying for Azure Marketplace services in non-USD currencies. If you are paying in USD, your pricing and billing will remain unchanged.
 
 | Currency | Price | Elastic Billing Units for Azure† |
 | --- | --- | --- |
@@ -46,9 +59,9 @@ These pricing changes will apply to customers who are currently paying for Azure
 † used to avoid rounding issues: at list price, 1 ECU corresponds to 10,000 Elastic Billing Units for Azure
 
 
-## How the changes will affect you [ec_how_the_changes_will_affect_you]
+## How the changes affect you [ec_how_the_changes_will_affect_you]
 
-For customers paying in non-USD currencies, any future prepaid fees, or on-demand usage after the plan change will be charged at the new currency exchange rate. The applicable rate will be clearly displayed on the Azure Marketplace listing page, allowing you to stay informed about the pricing adjustments. You will receive an email from Azure Marketplace once the plan change is in effect.
+For customers paying in non-USD currencies, any future prepaid fees, or on-demand usage after the plan/price change are charged at the new currency exchange rate. The applicable rate is clearly displayed on the Azure Marketplace listing page, allowing you to stay informed about the pricing adjustments. 
 
 
 ## Our commitment to you [ec_our_commitment_to_you]
diff --git a/deploy-manage/security/fips.md b/deploy-manage/security/fips.md
@@ -23,5 +23,7 @@ The Federal Information Processing Standard (FIPS) Publication 140-2, (FIPS PUB
 
 :::{note}
 If you are running {{es}} through {{eck}}, refer to [ECK FIPS compatibility](/deploy-manage/deploy/cloud-on-k8s/deploy-fips-compatible-version-of-eck.md).
+
+FIPS compliance is not officially supported in {{ece}} (ECE). While ECE may function on FIPS-enabled systems, this configuration has not been validated through our testing processes and is not recommended for production environments.
 :::
 
diff --git a/release-notes/elastic-cloud-serverless/known-issues.md b/release-notes/elastic-cloud-serverless/known-issues.md
@@ -16,6 +16,21 @@ Known issues are significant defects or limitations that may impact your impleme
 
 ## Active
 
+:::{dropdown} Entity store transform is unavailable 
+
+**Details**
+
+A new feature introduced to the entity store caused the transform to scan for nonexistent indices.
+
+**Workaround** 
+
+Restart the entity store:
+1. Find **Entity Store** in the navigation menu or by using the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md).
+2. On the **Entity Store** page, turn the toggle off.
+3. Turn the toggle back on.
+
+::::
+
 :::{dropdown} CSPM and Asset Management integrations don't ingest data when deployed using agent-based technology if {{kib}} is hosted on AWS
 Applies to: {{serverless-short}} deployments hosted on AWS
 
diff --git a/release-notes/elastic-security/known-issues.md b/release-notes/elastic-security/known-issues.md
@@ -16,6 +16,23 @@ Known issues are significant defects or limitations that may impact your impleme
 
 % :::
 
+:::{dropdown} Entity store transform is unavailable 
+
+Applies to: 9.2.0
+
+**Details**
+
+A new feature introduced to the entity store in 9.2.0 caused the transform to scan for nonexistent indices.
+
+**Workaround** 
+
+Restart the entity store:
+1. Find **Entity Store** in the navigation menu or by using the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md).
+2. On the **Entity Store** page, turn the toggle off.
+3. Turn the toggle back on.
+
+::::
+
 :::{dropdown} CSPM and Asset Management integrations don't ingest data when deployed using agent-based technology if {{kib}} is hosted on AWS
 Applies to: ECH 9.2.0 deployments hosted on AWS
 
diff --git a/solutions/observability/get-started/quickstart-elastic-cloud-otel-endpoint.md b/solutions/observability/get-started/quickstart-elastic-cloud-otel-endpoint.md
@@ -162,7 +162,10 @@ You must format your API key as `"Authorization": "ApiKey <api-key-value-here>"`
 
 ### Error: too many requests
 
-The Managed OTLP endpoint has per-project rate limits in place. If you reach this limit, reach out to our [support team](https://support.elastic.co). Refer to [Rate limiting](opentelemetry://reference/motlp.md#rate-limiting) for more information.
+If you see HTTP `429 Too Many Requests` errors when sending data through the Elastic Cloud Managed OTLP Endpoint (mOTLP) endpoint, your project might be hitting ingest rate limits.
+
+Refer to the dedicated [429 errors when using the Elastic Cloud Managed OTLP Endpoint](/troubleshoot/ingest/opentelemetry/429-errors-motlp.md) troubleshooting guide for details on causes, rate limits, and solutions.
+
 
 ## Provide feedback
 
diff --git a/troubleshoot/ingest/opentelemetry/429-errors-motlp.md b/troubleshoot/ingest/opentelemetry/429-errors-motlp.md
diff --git a/troubleshoot/toc.yml b/troubleshoot/toc.yml

Original file line number	Diff line number	Diff line change
`@@ -0,0 +1 @@`
	`1`	`+FIPS (Federal Information Processing Standards) compliance is not officially supported in ECE. While ECE may function on FIPS-enabled systems, this configuration has not been validated through our testing processes and is not recommended for production environments.`