You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am considering for a securityonion installation on multiple geographic zones, and I would like the data in each geographic zone to be resident in the region (e.g. US data in US and EU data in EU).
The idea is obviously a distributed architecture with receiver and searchnode residing in the different geographic areas. I was wondering if there was any way to define:
To which receivers the sensor can send data (can I define a subset of the receivers? or maybe just block the connections from firewall?)
To which searchnodes the specific receivers can send data
and then prevent elastic from rebalancing and sending data to searchnodes in different geographic areas, but only to those specified.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
I am considering for a securityonion installation on multiple geographic zones, and I would like the data in each geographic zone to be resident in the region (e.g. US data in US and EU data in EU).
The idea is obviously a distributed architecture with receiver and searchnode residing in the different geographic areas. I was wondering if there was any way to define:
and then prevent elastic from rebalancing and sending data to searchnodes in different geographic areas, but only to those specified.
Thanks in advance
Beta Was this translation helpful? Give feedback.
All reactions