From ad85c5a48bab46538d77f3568088669acd95dd9a Mon Sep 17 00:00:00 2001 From: Pete Gillin Date: Mon, 3 Nov 2025 18:32:22 +0000 Subject: [PATCH] Fix reindex-from-remote source host constraints The reindex documentation previously referenced the node setting needed to whitelist remote hosts. This does not apply to serverless. This change clarifies this, and documents the hosts allowed in serverless. --- specification/_global/reindex/ReindexRequest.ts | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/specification/_global/reindex/ReindexRequest.ts b/specification/_global/reindex/ReindexRequest.ts index 902c8ea528..594589e5a0 100644 --- a/specification/_global/reindex/ReindexRequest.ts +++ b/specification/_global/reindex/ReindexRequest.ts @@ -45,7 +45,8 @@ import { Destination, Source } from './types' * * To automatically create a data stream or index with a reindex API request, you must have the `auto_configure`, `create_index`, or `manage` index privilege for the destination data stream, index, or alias. * * If reindexing from a remote cluster, the `source.remote.user` must have the `monitor` cluster privilege and the `read` index privilege for the source data stream, index, or alias. * - * If reindexing from a remote cluster, you must explicitly allow the remote host in the `reindex.remote.whitelist` setting. + * If reindexing from a remote cluster into a cluster using Elastic Stack, you must explicitly allow the remote host using the `reindex.remote.whitelist` node setting on the destination cluster. + * If reindexing from a remote cluster into an Elastic Cloud Serverless project, only remote hosts from Elastic Cloud Hosted or Elastic Cloud Serverless are allowed. * Automatic data stream creation requires a matching index template with data stream enabled. * * The `dest` element can be configured like the index API to control optimistic concurrency control.