Manage engines - Administrator Guide - 8 - Cortex XSOAR - Cortex - Security Operations

Use separate load-balancing groups for different integrations and instances. Create Load-Balancing groups for certain tasks, which can help segregate the infrastructure of critical integrations.

Managed Security Service Providers may want to split internal engines and SaaS product engines.

If you have multiple AWS accounts that are not connected and do not want a single point of failure for AWS integrations that use STS.

Add/remove engines to a load-balancing group

You can only add the engine to the load-balancing group after you have connected the engine.

If you want to remove the last engine from a specific load-balancing group, if one or more integration instances use that engine, you will get an error. Before moving the engine, you need to assign Run on to a different engine or no engine for each of the integration instance settings.

Create load-balancing groups

When selecting Load-Balancing Group → Add to new group, you can create multiple load-balancing groups and decide which engines are part of each group.

Users can move an engine from one group to another. A group will be deleted when the last engine is removed from it.

Each engine can only belong to one group.