From da40420feb5dee0911a73a9597e18ff47c7b68bf Mon Sep 17 00:00:00 2001 From: Kuni Sen Date: Fri, 13 Jun 2025 10:39:15 +0900 Subject: [PATCH 1/4] Update differences-from-other-elasticsearch-offerings.md --- .../differences-from-other-elasticsearch-offerings.md | 10 ++++++++-- 1 file changed, 8 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 78d51b180b..d82c47102a 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 @@ -161,7 +161,11 @@ These recommendations do not apply to indices using better binary quantization ( ## Available {{es}} APIs [elasticsearch-differences-serverless-apis-availability] -Because {{serverless-full}} manages infrastructure automatically, certain Elasticsearch APIs are not available: +::::{important} +In {{serverless-full}}, configuration is limited to certain APIs, as Elastic automatically manages the infrastructure. As we are responsible for maintaining cluster stability, we make informed decisions about permissible actions to prevent unintended changes that could compromise service availability, performance, and data integrity, thereby ensuring the reliability of Serverless projects. +:::: + + Infrastructure operations : * All `_nodes/*` operations @@ -200,7 +204,9 @@ Refer to the [{{es-serverless}} API reference](https://www.elastic.co/docs/api/d ## Available {{es}} settings [elasticsearch-differences-serverless-settings-availability] -In {{serverless-full}} Elasticsearch projects, you can only configure [index-level settings](elasticsearch://reference/elasticsearch/index-settings/index.md). Cluster-level settings and node-level settings are fully managed by Elastic. +::::{important} +In {{serverless-full}} Elasticsearch projects, configuration is limited to certain [index-level settings](elasticsearch://reference/elasticsearch/index-settings/index.md), while Elastic fully manages cluster-level and node-level settings. As we are responsible for maintaining cluster stability, we make informed decisions about permissible actions to prevent unintended changes that could compromise service availability, performance, and data integrity, thereby ensuring the reliability of Serverless projects. +:::: Available settings : **Index-level settings**: Settings that control how documents are processed, stored, and searched are available to end users. These include: From f6b6fe47989ad081e64af8056b8ff1ef9aa3c3d9 Mon Sep 17 00:00:00 2001 From: Kuni Sen Date: Fri, 13 Jun 2025 10:46:18 +0900 Subject: [PATCH 2/4] Update differences-from-other-elasticsearch-offerings.md --- ...ences-from-other-elasticsearch-offerings.md | 18 ++++++++++++++++++ 1 file changed, 18 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 d82c47102a..184352e5f6 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 @@ -224,6 +224,24 @@ Managed settings * Shard allocation * Resource management +When attempting to use an unavailable index setting, you'll receive this error: + +```json +{ + "error": { + "root_cause": [ + { + "type": "illegal_argument_exception", + "reason": "Settings [xyz] are not available when running in serverless mode" + } + ], + "type": "illegal_argument_exception", + "reason": "Settings [xyz] are not available when running in serverless mode" + }, + "status": 400 +} +``` + ## Learn more - [{{serverless-full}} roadmap](https://www.elastic.co/cloud/serverless/roadmap): See upcoming features and development plans for the Serverless platform From 0cd17dcefbda680ed40bec7bee6a2a6112a9111d Mon Sep 17 00:00:00 2001 From: Kuni Sen <30574753+kunisen@users.noreply.github.com> Date: Wed, 18 Jun 2025 18:21:37 +0900 Subject: [PATCH 3/4] Update deploy-manage/deploy/elastic-cloud/differences-from-other-elasticsearch-offerings.md MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Edu González de la Herrán <25320357+eedugon@users.noreply.github.com> --- .../differences-from-other-elasticsearch-offerings.md | 5 ++--- 1 file changed, 2 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 184352e5f6..e77a3666b4 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 @@ -161,10 +161,9 @@ These recommendations do not apply to indices using better binary quantization ( ## Available {{es}} APIs [elasticsearch-differences-serverless-apis-availability] -::::{important} -In {{serverless-full}}, configuration is limited to certain APIs, as Elastic automatically manages the infrastructure. As we are responsible for maintaining cluster stability, we make informed decisions about permissible actions to prevent unintended changes that could compromise service availability, performance, and data integrity, thereby ensuring the reliability of Serverless projects. -:::: +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. +The following {{es}} APIs are not available in {{serverless-full}}: Infrastructure operations From cbfb66a11f0735f89049164f8bb2e4efc4617552 Mon Sep 17 00:00:00 2001 From: Kuni Sen <30574753+kunisen@users.noreply.github.com> Date: Wed, 18 Jun 2025 18:22:01 +0900 Subject: [PATCH 4/4] Update deploy-manage/deploy/elastic-cloud/differences-from-other-elasticsearch-offerings.md MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Edu González de la Herrán <25320357+eedugon@users.noreply.github.com> --- .../differences-from-other-elasticsearch-offerings.md | 4 +--- 1 file changed, 1 insertion(+), 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 e77a3666b4..86691454c3 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 @@ -203,9 +203,7 @@ Refer to the [{{es-serverless}} API reference](https://www.elastic.co/docs/api/d ## Available {{es}} settings [elasticsearch-differences-serverless-settings-availability] -::::{important} -In {{serverless-full}} Elasticsearch projects, configuration is limited to certain [index-level settings](elasticsearch://reference/elasticsearch/index-settings/index.md), while Elastic fully manages cluster-level and node-level settings. As we are responsible for maintaining cluster stability, we make informed decisions about permissible actions to prevent unintended changes that could compromise service availability, performance, and data integrity, thereby ensuring the reliability of Serverless projects. -:::: +In {{serverless-full}} {{es}} projects, configuration available to users is limited to certain [index-level settings](elasticsearch://reference/elasticsearch/index-settings/index.md), while Elastic manages cluster-level and node-level settings to maintain stability, availability, performance, and data integrity. These restrictions help ensure the reliability of Serverless projects. Available settings : **Index-level settings**: Settings that control how documents are processed, stored, and searched are available to end users. These include: