From dd6c7546e6b5c92de81f631fb9e405d37c6d0669 Mon Sep 17 00:00:00 2001 From: Visha Angelova Date: Fri, 7 Nov 2025 18:45:59 +0100 Subject: [PATCH 1/4] Add a known issue for agentless integrations --- .../get-started/_snippets/agentless-integrations-faq.md | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/solutions/security/get-started/_snippets/agentless-integrations-faq.md b/solutions/security/get-started/_snippets/agentless-integrations-faq.md index 9a726660e8..f7de227952 100644 --- a/solutions/security/get-started/_snippets/agentless-integrations-faq.md +++ b/solutions/security/get-started/_snippets/agentless-integrations-faq.md @@ -55,6 +55,11 @@ On the **{{fleet}}** page, agents associated with agentless integrations have na 3. From the **Actions** menu, select **Request diagnostics .zip**. 4. Download and unzip the [diagnostics bundle](/troubleshoot/ingest/fleet/common-problems.md#trb-collect-agent-diagnostics). Refer to [Common problems with {{fleet}} and {{agent}}](/troubleshoot/ingest/fleet/common-problems.md) for more information. +::::{note} +In {{ech}} deployments on {{stack}} versions 9.0.0-9.1.5, the connection between agentless integrations and {{fleet-server}} can be broken if the default {{fleet-server}} host URL value in {{fleet}} is modified or if a different host URL is set as the default. This can result in agentless agents having an `Unhealthy` status. + +This issue is resolved in {{stack}} 9.1.6 and 9.2.0. In these versions, agentless integration policies are assigned to a default managed {{fleet-server}} host which cannot be modified. +:::: ## How do I delete an agentless integration? [_how_do_i_delete_an_agentless_integration] @@ -72,4 +77,4 @@ When you create a new agentless CSPM integration, a new agent policy appears wit ## Can agentless integrations use a specific range of static IP addresses for configuring allow and deny rules for traffic? -No, agentless integrations can not use a specific range of static IP addresses for configuring ingress and egress allow and deny rules. +No, agentless integrations can not use a specific range of static IP addresses for configuring ingress and egress allow and deny rules. \ No newline at end of file From 9530fe30879ec46f1db3e86a739dd920d8ff01d3 Mon Sep 17 00:00:00 2001 From: Visha Angelova Date: Fri, 7 Nov 2025 21:35:34 +0100 Subject: [PATCH 2/4] Update based on review --- .../_snippets/agentless-integrations-faq.md | 12 +++++------- 1 file changed, 5 insertions(+), 7 deletions(-) diff --git a/solutions/security/get-started/_snippets/agentless-integrations-faq.md b/solutions/security/get-started/_snippets/agentless-integrations-faq.md index f7de227952..acf61c9936 100644 --- a/solutions/security/get-started/_snippets/agentless-integrations-faq.md +++ b/solutions/security/get-started/_snippets/agentless-integrations-faq.md @@ -37,8 +37,12 @@ To troubleshoot this issue: 1. Find **{{fleet}}** in the navigation menu or use the [global search field](/explore-analyze/find-and-organize/find-apps-and-objects.md). Go to the **Settings** tab. 2. Under **{{fleet}} server hosts**, click the **Actions** button for the policy named `Default`. This opens the Edit {{fleet}} Server flyout. The policy named `Default` should have the **Make this {{fleet}} server the default one** setting enabled. If not, enable it, then delete your integration and create it again. -::::{note} If the **Make this {{fleet}} server the default one** setting was already enabled but problems persist, it’s possible someone changed the default {{fleet}} server’s **URL** value. In this case, contact Elastic Support to find out what the original **URL** value was, update the settings to match this value, then delete your integration and create it again. + +::::{note} +In {{ech}} deployments on {{stack}} versions prior to 9.1.6, the connection between agentless integrations and {{fleet-server}} can be broken if the default {{fleet-server}} host URL value in {{fleet}} is modified or if a different host URL is set as the default. + +This issue is resolved in {{stack}} 9.1.6 and 9.2.0. In these versions, agentless integration policies are assigned to a default managed {{fleet-server}} host which cannot be modified. :::: ## Why can't I upgrade my agentless integration to a newer version? @@ -55,12 +59,6 @@ On the **{{fleet}}** page, agents associated with agentless integrations have na 3. From the **Actions** menu, select **Request diagnostics .zip**. 4. Download and unzip the [diagnostics bundle](/troubleshoot/ingest/fleet/common-problems.md#trb-collect-agent-diagnostics). Refer to [Common problems with {{fleet}} and {{agent}}](/troubleshoot/ingest/fleet/common-problems.md) for more information. -::::{note} -In {{ech}} deployments on {{stack}} versions 9.0.0-9.1.5, the connection between agentless integrations and {{fleet-server}} can be broken if the default {{fleet-server}} host URL value in {{fleet}} is modified or if a different host URL is set as the default. This can result in agentless agents having an `Unhealthy` status. - -This issue is resolved in {{stack}} 9.1.6 and 9.2.0. In these versions, agentless integration policies are assigned to a default managed {{fleet-server}} host which cannot be modified. -:::: - ## How do I delete an agentless integration? [_how_do_i_delete_an_agentless_integration] ::::{note} From dbe8751d842dddd102701aaabfe3ce788c29d3d3 Mon Sep 17 00:00:00 2001 From: Visha Angelova <91186315+vishaangelova@users.noreply.github.com> Date: Mon, 10 Nov 2025 11:13:58 +0100 Subject: [PATCH 3/4] Update solutions/security/get-started/_snippets/agentless-integrations-faq.md --- .../get-started/_snippets/agentless-integrations-faq.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/solutions/security/get-started/_snippets/agentless-integrations-faq.md b/solutions/security/get-started/_snippets/agentless-integrations-faq.md index acf61c9936..1c5c084d56 100644 --- a/solutions/security/get-started/_snippets/agentless-integrations-faq.md +++ b/solutions/security/get-started/_snippets/agentless-integrations-faq.md @@ -42,7 +42,7 @@ If the **Make this {{fleet}} server the default one** setting was already enable ::::{note} In {{ech}} deployments on {{stack}} versions prior to 9.1.6, the connection between agentless integrations and {{fleet-server}} can be broken if the default {{fleet-server}} host URL value in {{fleet}} is modified or if a different host URL is set as the default. -This issue is resolved in {{stack}} 9.1.6 and 9.2.0. In these versions, agentless integration policies are assigned to a default managed {{fleet-server}} host which cannot be modified. +This issue is resolved in {{stack}} 9.1.6. In this and later versions, agentless integration policies are assigned to a default managed {{fleet-server}} host which cannot be modified. :::: ## Why can't I upgrade my agentless integration to a newer version? From b5e4953f4cc293deeb5f529a91d322e3e4338b75 Mon Sep 17 00:00:00 2001 From: Visha Angelova <91186315+vishaangelova@users.noreply.github.com> Date: Mon, 10 Nov 2025 19:14:05 +0100 Subject: [PATCH 4/4] Update solutions/security/get-started/_snippets/agentless-integrations-faq.md Co-authored-by: florent-leborgne --- .../get-started/_snippets/agentless-integrations-faq.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/solutions/security/get-started/_snippets/agentless-integrations-faq.md b/solutions/security/get-started/_snippets/agentless-integrations-faq.md index 1c5c084d56..9d992b535d 100644 --- a/solutions/security/get-started/_snippets/agentless-integrations-faq.md +++ b/solutions/security/get-started/_snippets/agentless-integrations-faq.md @@ -40,7 +40,8 @@ To troubleshoot this issue: If the **Make this {{fleet}} server the default one** setting was already enabled but problems persist, it’s possible someone changed the default {{fleet}} server’s **URL** value. In this case, contact Elastic Support to find out what the original **URL** value was, update the settings to match this value, then delete your integration and create it again. ::::{note} -In {{ech}} deployments on {{stack}} versions prior to 9.1.6, the connection between agentless integrations and {{fleet-server}} can be broken if the default {{fleet-server}} host URL value in {{fleet}} is modified or if a different host URL is set as the default. +:applies_to: ess: ga +In {{ech}} deployments on {{stack}} versions prior to 9.1.6, the connection between agentless integrations and {{fleet-server}} can break if the default {{fleet-server}} host URL value in {{fleet}} is modified or if a different host URL is set as the default. This issue is resolved in {{stack}} 9.1.6. In this and later versions, agentless integration policies are assigned to a default managed {{fleet-server}} host which cannot be modified. ::::