Fortinet white logo
Fortinet white logo

Prepare to deploy FortiSOAR

Prepare to deploy FortiSOAR

Before you begin the actual deployment of FortiSOAR, it is recommended that you complete the site preparations, including reviewing the sizing requirements and setting up the server with the appropriate hardware configuration.

Review the sizing and configuration

Use the FortiSOAR Sizing Guide to identify the right configuration for your anticipated workload. In release 7.6.1, a new CLI option for optimal resource configuration is added, which enables you to apply a configuration to tune all FortiSOAR services for the efficient use of available hardware resources, such as vCPU and RAM. For details, see the FortiSOAR Admin CLI chapter in the "Administration Guide."

Choose the platform and specifications

If you are using the OVA to deploy FortiSOAR, provision to import the FortiSOAR virtual appliance into VMware or AWS.
Alternatively, if you are installing FortiSOAR using the installation script, before deployment, ensure that you have setup a system with either Rocky Linux version 9.3/9.4/9.5 or RHEL version 9.3/9.4/9.5. Note that release 7.6.1 has been tested with RHEL 9.5 and Rocky Linux 9.5.

Virtual Machine (VM) recommended specifications:

  • 12 available vCPUs
  • 48 GB available RAM
  • 1 TB available disk space: Recommended to have high-performance storage, preferably SSDs.
  • 1 vNIC

Choose from the following supported hypervisors:

  • On Premises
    • VMware ESXi versions 5.5, 6.0, 6.5, 7.0, and 8.0
    • Redhat KVM
  • Cloud
    • FortiSOAR Cloud
    • AWS Cloud
  • Docker
Note

For any other virtualization or cloud hosting environment, such as GCP, Azure, OCI, or OCI DRCC, you can install Rocky Linux 9.3/9.4/9.5 or RHEL 9.3/9.4/9.5 and then install FortiSOAR using the FortiSOAR CLI installer. Note that release 7.6.1 has been tested with RHEL 9.5 and Rocky Linux 9.5. See the Deployment Guide for details.

Prepare to deploy FortiSOAR

Prepare to deploy FortiSOAR

Before you begin the actual deployment of FortiSOAR, it is recommended that you complete the site preparations, including reviewing the sizing requirements and setting up the server with the appropriate hardware configuration.

Review the sizing and configuration

Use the FortiSOAR Sizing Guide to identify the right configuration for your anticipated workload. In release 7.6.1, a new CLI option for optimal resource configuration is added, which enables you to apply a configuration to tune all FortiSOAR services for the efficient use of available hardware resources, such as vCPU and RAM. For details, see the FortiSOAR Admin CLI chapter in the "Administration Guide."

Choose the platform and specifications

If you are using the OVA to deploy FortiSOAR, provision to import the FortiSOAR virtual appliance into VMware or AWS.
Alternatively, if you are installing FortiSOAR using the installation script, before deployment, ensure that you have setup a system with either Rocky Linux version 9.3/9.4/9.5 or RHEL version 9.3/9.4/9.5. Note that release 7.6.1 has been tested with RHEL 9.5 and Rocky Linux 9.5.

Virtual Machine (VM) recommended specifications:

  • 12 available vCPUs
  • 48 GB available RAM
  • 1 TB available disk space: Recommended to have high-performance storage, preferably SSDs.
  • 1 vNIC

Choose from the following supported hypervisors:

  • On Premises
    • VMware ESXi versions 5.5, 6.0, 6.5, 7.0, and 8.0
    • Redhat KVM
  • Cloud
    • FortiSOAR Cloud
    • AWS Cloud
  • Docker
Note

For any other virtualization or cloud hosting environment, such as GCP, Azure, OCI, or OCI DRCC, you can install Rocky Linux 9.3/9.4/9.5 or RHEL 9.3/9.4/9.5 and then install FortiSOAR using the FortiSOAR CLI installer. Note that release 7.6.1 has been tested with RHEL 9.5 and Rocky Linux 9.5. See the Deployment Guide for details.