Engine in cloud - design concept

ahmad — Wed, 19 Feb 2025 08:41:46 GMT

I have a cloud instance of XSOAR, with set of technologies in cloud and on prem as well, my initial thought is to have an engine for each group, that means two engines, and separate the technologies accordingly, any thought on that and what is challenges, pros and cons?

Re: Engine in cloud - design concept

elmitchell — Mon, 24 Feb 2025 20:00:43 GMT

Hello @ahmad, first I would ask is you XSOAR instance and the technologies you need to access in the cloud on the same networks? if so then you likely do not need an engine for the cloud. If you do need an engine for the cloud then as long as it can reach your on-prem resources and the cloud resources there is no need to create two separate engines. If the cloud infrastructure cannot reach the on-prem infrastructure then you would need to have 2 separate engines one for the your cloud integrations and one for your on-prem integrations. Overall one engine would be more preferred as it is less overhead for you but that call also depend on the number of integrations you plan on connecting through the engine. Overall if a single engine can reach the integrations in both environments then that would be the preferred architecture.

topic Re: Engine in cloud - design concept in Cortex XSOAR Discussions

Engine in cloud - design concept

Re: Engine in cloud - design concept