From af5ddd2dfcbc1c83d7d89e090a3611d89e98afd9 Mon Sep 17 00:00:00 2001 From: Vlada Chirmicci Date: Tue, 17 Feb 2026 16:15:48 +0000 Subject: [PATCH 1/6] Adding info on index limits per project Relates to #5164 --- .../differences-from-other-elasticsearch-offerings.md | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/deploy-manage/deploy/elastic-cloud/differences-from-other-elasticsearch-offerings.md b/deploy-manage/deploy/elastic-cloud/differences-from-other-elasticsearch-offerings.md index 66a46eeaae..21a7ad6920 100644 --- a/deploy-manage/deploy/elastic-cloud/differences-from-other-elasticsearch-offerings.md +++ b/deploy-manage/deploy/elastic-cloud/differences-from-other-elasticsearch-offerings.md @@ -172,6 +172,16 @@ If you expect that you will have large datasets that exceed the recommended maxi These recommendations do not apply to indices using better binary quantization (BBQ). Refer to [vector quantization](elasticsearch://reference/elasticsearch/mapping-reference/dense-vector.md#dense-vector-quantization) for more information. +### Index and resource limits + +{{serverless-full}} applies certain project-level limits to ensure reliable performance and stability. + +| Limit | Value | Adjustable | +| :--- | :--- | :--- | +| Number of indices per project | 15,000 | Yes | + +Some index limits are adjustable and can be increased by request, while others are fixed. To request a limit increase, open a support case and include the limit you want to increase, your preferred new value, and a brief description of your use case. Providing meaningful details around your use case and desired outcome ensures that Elastic can make recommendations that best suit your workload. + ## Available {{es}} APIs [elasticsearch-differences-serverless-apis-availability] In {{serverless-full}}, access is limited to a subset of {{es}} APIs, as Elastic manages the underlying infrastructure. These restrictions help maintain cluster stability, availability, and data integrity, ensuring reliable operation of Serverless projects. From 35f28c257d8ad360436751d7e0fed1101ca13e63 Mon Sep 17 00:00:00 2001 From: Vlada Chirmicci Date: Tue, 17 Feb 2026 16:25:16 +0000 Subject: [PATCH 2/6] Add context about limits on the Serverless overview page --- .../differences-from-other-elasticsearch-offerings.md | 2 +- deploy-manage/deploy/elastic-cloud/serverless.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/deploy-manage/deploy/elastic-cloud/differences-from-other-elasticsearch-offerings.md b/deploy-manage/deploy/elastic-cloud/differences-from-other-elasticsearch-offerings.md index 21a7ad6920..70706f8dbf 100644 --- a/deploy-manage/deploy/elastic-cloud/differences-from-other-elasticsearch-offerings.md +++ b/deploy-manage/deploy/elastic-cloud/differences-from-other-elasticsearch-offerings.md @@ -172,7 +172,7 @@ If you expect that you will have large datasets that exceed the recommended maxi These recommendations do not apply to indices using better binary quantization (BBQ). Refer to [vector quantization](elasticsearch://reference/elasticsearch/mapping-reference/dense-vector.md#dense-vector-quantization) for more information. -### Index and resource limits +### Index and resource limits [index-and-resource-limits] {{serverless-full}} applies certain project-level limits to ensure reliable performance and stability. diff --git a/deploy-manage/deploy/elastic-cloud/serverless.md b/deploy-manage/deploy/elastic-cloud/serverless.md index a229986c38..23075a9aae 100644 --- a/deploy-manage/deploy/elastic-cloud/serverless.md +++ b/deploy-manage/deploy/elastic-cloud/serverless.md @@ -43,7 +43,7 @@ Afterwards, you can: **Management free:** Elastic manages the underlying Elastic cluster, so you can focus on your data. With serverless projects, Elastic is responsible for automatic upgrades, data backups, and business continuity. -**Autoscaled:** To meet your performance requirements, the system automatically adjusts to your workloads. For example, when you have a short time spike on the data you ingest, more resources are allocated for that period of time. When the spike is over, the system uses less resources, without any action on your end. +**Autoscaled:** To meet your performance requirements, the system automatically adjusts to your workloads. For example, when you have a short time spike on the data you ingest, more resources are allocated for that period of time. When the spike is over, the system uses less resources, without any action on your end. Some [project-level limits](/deploy-manage/deploy/elastic-cloud/differences-from-other-elasticsearch-offerings.md#index-and-resource-limits) apply to ensure performance and stability. Certain limits are adjustable by request. **Optimized data storage:** Your data is stored in cost-efficient, general storage. A cache layer is available on top of the general storage for recent and frequently queried data that provides faster search speed. The size of the cache layer and the volume of data it holds depend on [settings](../../../deploy-manage/deploy/elastic-cloud/project-settings.md) that you can configure for each project. From cd770341f7d5445cddd8f5404c76e54590cec256 Mon Sep 17 00:00:00 2001 From: Vlada Chirmicci Date: Wed, 18 Feb 2026 11:43:19 +0000 Subject: [PATCH 3/6] Add note about index limits with links --- manage-data/data-store/index-basics.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/manage-data/data-store/index-basics.md b/manage-data/data-store/index-basics.md index 2e5eaa3084..90d4895064 100644 --- a/manage-data/data-store/index-basics.md +++ b/manage-data/data-store/index-basics.md @@ -19,6 +19,11 @@ An index is a fundamental unit of storage in {{es}}. It is a collection of docum A closely related concept is a [data stream](/manage-data/data-store/data-streams.md). This index abstraction is optimized for append-only timestamped data, and is made up of hidden, auto-generated backing indices. If you’re working with timestamped data, we recommend the [Elastic Observability](/solutions/observability/get-started.md) solution for additional tools and optimized content. :::: +:::{note} +:applies_to: {"serverless": "ga"} +In {{serverless-full}}, each project supports up to 15,000 indices. This limit helps ensure reliable performance and stability. If you need a higher limit, you can [request an increase](/deploy-manage/deploy/elastic-cloud/differences-from-other-elasticsearch-offerings.md#index-and-resource-limits). For index sizing recommendations, refer to [index sizing guidelines](/deploy-manage/deploy/elastic-cloud/differences-from-other-elasticsearch-offerings.md#elasticsearch-differences-serverless-index-size). +::: + ## Index components An index is made up of the following components. From f689b61445e884fe16e0d9c2478b08d6a030ab88 Mon Sep 17 00:00:00 2001 From: Vlada Chirmicci Date: Thu, 19 Feb 2026 10:59:16 +0000 Subject: [PATCH 4/6] Minor language adjustments around limits/limit --- .../differences-from-other-elasticsearch-offerings.md | 4 ++-- deploy-manage/deploy/elastic-cloud/serverless.md | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/deploy-manage/deploy/elastic-cloud/differences-from-other-elasticsearch-offerings.md b/deploy-manage/deploy/elastic-cloud/differences-from-other-elasticsearch-offerings.md index 70706f8dbf..7b8d31e46e 100644 --- a/deploy-manage/deploy/elastic-cloud/differences-from-other-elasticsearch-offerings.md +++ b/deploy-manage/deploy/elastic-cloud/differences-from-other-elasticsearch-offerings.md @@ -174,13 +174,13 @@ These recommendations do not apply to indices using better binary quantization ( ### Index and resource limits [index-and-resource-limits] -{{serverless-full}} applies certain project-level limits to ensure reliable performance and stability. +{{serverless-full}} applies the following project-level limit to ensure reliable performance and stability. | Limit | Value | Adjustable | | :--- | :--- | :--- | | Number of indices per project | 15,000 | Yes | -Some index limits are adjustable and can be increased by request, while others are fixed. To request a limit increase, open a support case and include the limit you want to increase, your preferred new value, and a brief description of your use case. Providing meaningful details around your use case and desired outcome ensures that Elastic can make recommendations that best suit your workload. +The index limit is adjustable and can be increased by request, while others are fixed. To request a limit increase, open a support case and include the limit you want to increase, your preferred new value, and a brief description of your use case. Providing meaningful details around your use case and desired outcome ensures that Elastic can make recommendations that best suit your workload. ## Available {{es}} APIs [elasticsearch-differences-serverless-apis-availability] diff --git a/deploy-manage/deploy/elastic-cloud/serverless.md b/deploy-manage/deploy/elastic-cloud/serverless.md index 23075a9aae..25d392bccc 100644 --- a/deploy-manage/deploy/elastic-cloud/serverless.md +++ b/deploy-manage/deploy/elastic-cloud/serverless.md @@ -43,7 +43,7 @@ Afterwards, you can: **Management free:** Elastic manages the underlying Elastic cluster, so you can focus on your data. With serverless projects, Elastic is responsible for automatic upgrades, data backups, and business continuity. -**Autoscaled:** To meet your performance requirements, the system automatically adjusts to your workloads. For example, when you have a short time spike on the data you ingest, more resources are allocated for that period of time. When the spike is over, the system uses less resources, without any action on your end. Some [project-level limits](/deploy-manage/deploy/elastic-cloud/differences-from-other-elasticsearch-offerings.md#index-and-resource-limits) apply to ensure performance and stability. Certain limits are adjustable by request. +**Autoscaled:** To meet your performance requirements, the system automatically adjusts to your workloads. For example, when you have a short time spike on the data you ingest, more resources are allocated for that period of time. When the spike is over, the system uses less resources, without any action on your end. Some project-level limits apply to ensure performance and stability, including a [limit on the number of indices per project](/deploy-manage/deploy/elastic-cloud/differences-from-other-elasticsearch-offerings.md#index-and-resource-limits) that can be adjusted by request. **Optimized data storage:** Your data is stored in cost-efficient, general storage. A cache layer is available on top of the general storage for recent and frequently queried data that provides faster search speed. The size of the cache layer and the volume of data it holds depend on [settings](../../../deploy-manage/deploy/elastic-cloud/project-settings.md) that you can configure for each project. From 84161786b59ba726a86dac57b96f7e56a650062a Mon Sep 17 00:00:00 2001 From: Fabrizio Ferri Benedetti Date: Thu, 19 Feb 2026 12:29:59 +0100 Subject: [PATCH 5/6] Fix Managed OTLP Endpoint link (remove extra slash) Normalize opentelemetry:///reference/motlp.md to opentelemetry://reference/motlp.md for consistency with other opentelemetry crosslinks in the file. Co-authored-by: Cursor Co-authored-by: Claude --- .../differences-from-other-elasticsearch-offerings.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/deploy-manage/deploy/elastic-cloud/differences-from-other-elasticsearch-offerings.md b/deploy-manage/deploy/elastic-cloud/differences-from-other-elasticsearch-offerings.md index 7b8d31e46e..47bfd7af40 100644 --- a/deploy-manage/deploy/elastic-cloud/differences-from-other-elasticsearch-offerings.md +++ b/deploy-manage/deploy/elastic-cloud/differences-from-other-elasticsearch-offerings.md @@ -132,7 +132,7 @@ This table compares Observability capabilities between {{ech}} deployments and O | **[Kibana Alerts](/deploy-manage/monitor/monitoring-data/configure-stack-monitoring-alerts.md)** | ✅ | ✅ | | | **[LogsDB index mode](/manage-data/data-store/data-streams/logs-data-stream.md)** | ✅ | ✅ | - Reduces storage footprint
- Enabled by default
- Cannot be disabled | | **[Logs management](/solutions/observability/logs.md)** | ✅ | ✅ | | -| **[Managed OTLP Endpoint](opentelemetry:///reference/motlp.md)** | ✅ | ✅ | | +| **[Managed OTLP Endpoint](opentelemetry://reference/motlp.md)** | ✅ | ✅ | | | **[Metrics monitoring](/solutions/observability/apm/metrics.md)** | ✅ | ✅ | | | **[Observability SLO](/solutions/observability/incident-management/service-level-objectives-slos.md)** | ✅ | ✅ | | | [**Real User Monitoring (RUM)**](/solutions/observability/applications/user-experience.md) | ✅ | **Planned** | Anticipated in a future release | From da6d765ebcee09ae10e7c8191f18bf95a8ff1fdc Mon Sep 17 00:00:00 2001 From: Vlada Chirmicci Date: Thu, 19 Feb 2026 14:52:28 +0000 Subject: [PATCH 6/6] Update deploy-manage/deploy/elastic-cloud/differences-from-other-elasticsearch-offerings.md Co-authored-by: David Kilfoyle <41695641+kilfoyle@users.noreply.github.com> --- .../differences-from-other-elasticsearch-offerings.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/deploy-manage/deploy/elastic-cloud/differences-from-other-elasticsearch-offerings.md b/deploy-manage/deploy/elastic-cloud/differences-from-other-elasticsearch-offerings.md index 47bfd7af40..bd957f08f6 100644 --- a/deploy-manage/deploy/elastic-cloud/differences-from-other-elasticsearch-offerings.md +++ b/deploy-manage/deploy/elastic-cloud/differences-from-other-elasticsearch-offerings.md @@ -180,7 +180,7 @@ These recommendations do not apply to indices using better binary quantization ( | :--- | :--- | :--- | | Number of indices per project | 15,000 | Yes | -The index limit is adjustable and can be increased by request, while others are fixed. To request a limit increase, open a support case and include the limit you want to increase, your preferred new value, and a brief description of your use case. Providing meaningful details around your use case and desired outcome ensures that Elastic can make recommendations that best suit your workload. +The index limit is adjustable and can be increased by request, while others are fixed. To request a limit increase, open a support case, and include your preferred new value and a brief description of your use case. Providing meaningful details around your use case and desired outcome ensures that Elastic can make recommendations that best suit your workload. ## Available {{es}} APIs [elasticsearch-differences-serverless-apis-availability]