From 72f069b10889113ba9be6db38c300d881ac0b9ec Mon Sep 17 00:00:00 2001 From: Vignesh Shanmugam Date: Wed, 19 Nov 2025 11:52:43 -0800 Subject: [PATCH 1/3] Update motlp availability in ECH regions + Add the list of supported regions for ECH Tech Preview --- docs/reference/motlp.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/reference/motlp.md b/docs/reference/motlp.md index 4fadd624..7e5e8b9b 100644 --- a/docs/reference/motlp.md +++ b/docs/reference/motlp.md @@ -51,6 +51,10 @@ To use the {{ecloud}} {{motlp}} you need the following: You don't need APM Server when ingesting data through the Managed OTLP Endpoint. The APM integration (`.apm` endpoint) is a legacy ingest path that only supports traces and translates OTLP telemetry to ECS, whereas {{motlp}} natively ingests OTLP data. ::: +:::{note} +For {{ech}} deployments, Managed OTLP endpoint is current supported in the following AWS regions: ap-southeast-1, ap-northeast-1, ap-south-1, eu-west-1, eu-west-2, us-east-1, us-west-2, us-east-2. Support for additional regions/CSP's is in progress and will be expanded over time. +::: + ## Send data to Elastic To send data to Elastic through the {{motlp}}, follow the [Send data to the Elastic Cloud Managed OTLP Endpoint](docs-content://solutions/observability/get-started/quickstart-elastic-cloud-otel-endpoint.md) quickstart. From a63c6a67f304b33758b55d511a5dd471ebe97150 Mon Sep 17 00:00:00 2001 From: Vignesh Shanmugam Date: Wed, 19 Nov 2025 20:58:17 -0800 Subject: [PATCH 2/3] Update docs/reference/motlp.md Co-authored-by: Andrew Wilkins --- docs/reference/motlp.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/reference/motlp.md b/docs/reference/motlp.md index 7e5e8b9b..25c7915d 100644 --- a/docs/reference/motlp.md +++ b/docs/reference/motlp.md @@ -52,7 +52,7 @@ You don't need APM Server when ingesting data through the Managed OTLP Endpoint. ::: :::{note} -For {{ech}} deployments, Managed OTLP endpoint is current supported in the following AWS regions: ap-southeast-1, ap-northeast-1, ap-south-1, eu-west-1, eu-west-2, us-east-1, us-west-2, us-east-2. Support for additional regions/CSP's is in progress and will be expanded over time. +For {{ech}} deployments, Managed OTLP endpoint is current supported in the following AWS regions: ap-southeast-1, ap-northeast-1, ap-south-1, eu-west-1, eu-west-2, us-east-1, us-west-2, us-east-2. Support for additional regions and cloud providers is in progress and will be expanded over time. ::: ## Send data to Elastic From aa13a1aec6806c9664947cdb4551da7075d4eb1a Mon Sep 17 00:00:00 2001 From: Fabrizio Ferri-Benedetti Date: Thu, 20 Nov 2025 09:06:42 +0100 Subject: [PATCH 3/3] Update motlp.md --- docs/reference/motlp.md | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/docs/reference/motlp.md b/docs/reference/motlp.md index 25c7915d..940358d8 100644 --- a/docs/reference/motlp.md +++ b/docs/reference/motlp.md @@ -47,12 +47,11 @@ To use the {{ecloud}} {{motlp}} you need the following: - [EDOT Cloud Forwarder](/reference/edot-cloud-forwarder/index.md) - Any other forwarder that supports the OTLP protocol. -:::{note} You don't need APM Server when ingesting data through the Managed OTLP Endpoint. The APM integration (`.apm` endpoint) is a legacy ingest path that only supports traces and translates OTLP telemetry to ECS, whereas {{motlp}} natively ingests OTLP data. -::: :::{note} -For {{ech}} deployments, Managed OTLP endpoint is current supported in the following AWS regions: ap-southeast-1, ap-northeast-1, ap-south-1, eu-west-1, eu-west-2, us-east-1, us-west-2, us-east-2. Support for additional regions and cloud providers is in progress and will be expanded over time. +For {{ech}} deployments, {{motlp}} is currently supported in the following AWS regions: ap-southeast-1, ap-northeast-1, ap-south-1, eu-west-1, eu-west-2, us-east-1, us-west-2, us-east-2. +Support for additional regions and cloud providers is in progress and will be expanded over time. ::: ## Send data to Elastic