SSE solution or Stand Alone Fleet Node ? #14525
Replies: 1 comment
-
The standalone Fleet Server serves two purposes -- it updates and configures the Elastic Agents deployed to your endpoints, and it also acts as a log receiver. Any solution you put in place would need to be able to route traffic in both directions. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I am looking at an enterprise remote connectivity platform like Zscaler or Netskope.
Would this remove the need for the stand-alone fleet server? Assuming the private application access is created for the endpoints to communicate with the Manager node. It would be essentially running an always on VPN and route any host generated traffic destined for the Manager node over the SSE connection. I believe only the clients can push to the server though. Any idea if this would work for ingesting logs from remote endpoints or would it only allow SOC access?
Beta Was this translation helpful? Give feedback.
All reactions