Skip to content

[8.x] Update warning for Elastic Defend with Remote ES cluster (backport #1759) #1781

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Apr 28, 2025
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -7,9 +7,13 @@ Beginning in version 8.12.0, you can send {agent} data to a remote {es} cluster.

A remote {es} cluster supports the same <<es-output-settings,output settings>> as your main {es} cluster.

WARNING: A bug has been found that causes {elastic-defend} response actions to stop working when a remote {es} output is configured for an agent. This bug is currently being investigated and is expected to be resolved in an upcoming release.
[NOTE]
====
Note the following restrictions with the remote {es} output:

NOTE: Using a remote {es} output with a target cluster that has {cloud}/ec-traffic-filtering-deployment-configuration.html[traffic filters] enabled is not currently supported.
* Using a remote {es} output with a target cluster that has {cloud}/ec-traffic-filtering-deployment-configuration.html[traffic filters] enabled is not currently supported.
* Using {elastic-defend} is currently not supported when a remote {es} output is configured for an agent.
====

To configure a remote {es} cluster for your {agent} data:

Expand Down