Multi-tenant server requirements and examples.
Note
Exact sizing specifications vary depending on several factors, including the number of incidents ingested, the number of indicators in the system, playbook usage, and so on.
Each host and tenant is a standalone instance of the Cortex XSOAR server and must meet the minimum sizing recommendations for a production environment.
Example Multi-Tenant Deployment
This example details the sizing requirements for a single host that has two tenants.
The hardware requirements for this deployment are:
Component | Calculation | Production Requirements |
|---|---|---|
CPU | (1 host plus 2 tenants) x 16 CPU cores | 48 CPU cores |
Memory | (1 host plus 2 tenants) x 32 GB RAM | 96 GB RAM |
Storage | Production Minimum | 1 TB SSD with minimum 3k dedicated IOPS |
Example Sizing Comparison Between Elasticsearch and Bolt Database for Known Capacity
In this example where the number of incidents and commands is known, the sizing requirements for Elasticsearch and Bolt database are based on:
Approximately 50 incidents per day, per tenant, with each incident running 50 commands/scripts.
For engines:
The specifications for each engine are 16 CPU and 32 GB RAM.
The engine is defined for each integration, including those that fetch incidents.
Incidents were fetched using the Splunk integration and executed using this playbook.
The following displays the sizing comparison for a known capacity.
Database | Server CPU | Server Memory | Server IOPS | Number of Tenants w/ Engine | Number of Tenants w/o Engine |
|---|---|---|---|---|---|
Elasticsearch | 36 cores | 72 GB | N/A | 54 | 40 |
Bolt | 36 cores | 72 GB | 3000 | 52 | 32 |