Engine in cloud - design concept

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Engine in cloud - design concept

L0 Member

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?

Cortex XSOAR  

1 REPLY 1

L2 Linker

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.

  • 190 Views
  • 1 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!