Manual: Multi-node HA-ready production profile requirements and installation

This page walks you through the requirements and installation instructions for the multi-node HA-ready production profile.

Deployment Profile Overview

Important:

Linux and Kubernetes knowledge is required regardless of the deployment profile you choose. If you encounter issues installing and configuring Automation Suite, contact UiPath Professional Services.

Before choosing your deployment profile, see Supported use cases for single-node and multi-node installations.

The installation process generates self-signed certificates on your behalf. These certificates will expire in 90 days, and you must replace them with certificates signed by a trusted Certificate Authority (CA) as soon as installation completes. If you do not update the certificates, the installation will stop working after 90 days. For instructions, see Managing certificates.

The multi-node HA-ready production profile is resilient to only one node failure. This means that you can lose only one server node. This restriction does not apply to agent nodes. You can lose as many agent nodes and still continue to use the cluster without downtime as long as enough overall cluster capacity is available.

Federal Information Processing Standard (FIPS) is not compatible with Automation Suite. If FIPs is enabled at any point on the servers running Automation Suite, the cluster will fail. If FIPs is enabled on any cluster server, the installer will encounter issues blocking the installation.

Larger node sizes are more efficient than smaller node sizes because of the fixed baseline resource overhead per node. For example, 3 x 32 cores nodes is more efficient than 6 x 16 cores nodes.

Deployment profile	Prerequisites	Requirements	Configuration	Installation
Multi-node HA-ready production profile	Minimum 3 Linux machines (RHEL 8.6, 8.8) with ipcalc tool installed: Additional Linux machine is required when using Task Mining Additional Linux machine with GPU support is recommended when using Document Understanding Note: We support new minor versions of RHEL within 90 days of their release. We support SELinux with default policies.	Multi-node HA-ready production machine requirements	Configuring the machines	Online multi-node HA-ready production installation Offline multi-node HA-ready production installation
	Microsoft SQL Server (2016, 2017, 2019, 2022 - Standard and Enterprise editions) Additional Microsoft SQL platforms, such as Azure SQL Database or Azure SQL Managed Instance, as well as Amazon Relational Database Service are also supported as long as the Microsoft SQL Server database engine meets the requirements.	MS SQL Server requirements	Configuring MS SQL Server
	DNS	N/A	Configuring the DNS
	IPv4 Important: IPv6 is not supported.	N/A	N/A
	Trusted TLS, token-signing and SQL connection encryption certificates	N/A	Configuring the certificates
	Load balancer	N/A	Configuring the load balancer
	Proxy server (optional)	N/A	Configuring proxy on the machine Configuring proxy during installation
	Setting up Kerberos authentication (optional)	N/A	Setting up Kerberos authentication

Attention:

• You need root permission to install and deploy Automation Suite. For more on the specific components that require root access, see Root privileges requirement.
• Having scan agents running on your system may cause installation or runtime failures, due to the changes they make to the IPTables. To avoid this behavior, configure your scan agent so that it does not interfere with the Automation Suite installation.
• UiPath does not prescribe specific firewall or developer tool configurations as long as the Automation Suite requirements are met. Based on our observations, a limited number of external tools can interfere with the smooth operation of Automation Suite. If such issues arise, contact the relevant vendor for help. For additional guidance, see the Automation Suite responsibility matrix.

Production Deployment — Multi-node HA-ready Production Profile Hardware Requirements

Important:

The minimum hardware requirements do not protect the deployment from node failures.

To understand your storage needs and plan for them accordingly, see Evaluating your storage needs.

The multi-node HA-ready production profile is resilient to only one node failure. This means that you can lose only one server node. This restriction does not apply to agent nodes. You can lose as many agent nodes and still continue to use the cluster without downtime as long as enough overall cluster capacity is available.

Federal Information Processing Standard (FIPS) is not compatible with Automation Suite. If FIPs is enabled at any point on the servers running Automation Suite, the cluster will fail. If FIPs is enabled on any cluster server, the installer will encounter issues blocking the installation.

If you opt for the multi-node HA-ready production profile, you must meet the following hard requirements:

Multi-node HA-ready production profile (the only configuration supported for production deployments)
Selection	Complete	Basic
Node count	At least 3 server nodes. There must be an odd number of server nodes in a cluster to have increased fault tolerance. There is no limit on the number of agent nodes
Processor	96 (v-)CPU/cores	48 (v-)CPU/cores
Minimum processor per node	16 (v-)CPU/cores	16 (v-)CPU/cores
RAM total	192 GiB	96 GiB
Minimum RAM per node	32 GiB	32 GiB
Cluster binaries and state disk for each node	256 GiB SSD Min IOPS: 1100	256 GiB SSD Min IOPS: 1100
Data disk for each server node	2 TiB SSD Min IOPS: 1100	512 GiB SSD Min IOPS: 1100
etcd disk for each server node	16 GiB SSD Min IOPS: 240	16 GiB SSD Min IOPS: 240
UiPath bundle disk (For offline installation only, on one of the server nodes)	512 GiB SSD Min IOPS: 1100	512 GiB SSD Min IOPS: 1100
Additional agent node for Task Mining (required)
Processor	20 (v-)CPU/cores	N/A (Task Mining is not present in this selection)
RAM	60 GiB
Cluster binaries and state disk	256 GiB SSD Min IOPS: 1100
Data disk	N/A
Additional agent node with GPU support for Document Understanding (strongly recommended)
Processor	8 (v-)CPU/cores	N/A (AI Center is not present in this selection)
RAM	52 GiB
Cluster binaries and state disk	256 GiB SSD Min IOPS: 1100
Data disk	N/A
GPU RAM	11 GiB

Note: Larger node sizes are more efficient than smaller node sizes because of the fixed baseline resource overhead per node. For example, 3 x 32 cores nodes is more efficient than 6 x 16 cores nodes.

Microsoft SQL Server general requirements

The installation requires an external SQL server as a prerequisite.

Note: Make sure that the SQL server can be accessed from each cluster VM.

Microsoft SQL Server 2016, 2017, 2019, and 2022 Standard and Enterprise editions are supported.

The minimum hardware requirements for Microsoft SQL Server are:

• 8 (v-)CPU
• 32 GiB RAM
• 256 GiB SSD

Configuring the Certificates

This page explains what certificate configuration entails at the time of installation.

The installation process generates self-signed certificates on your behalf. You must replace them with certificates signed by a trusted Certificate Authority (CA) as soon as installation completes. If you do not update the certificates, the installation will stop working after 90 days.

Aside from the above certificates, you may need to provide additional trusted CA certificates if you want the cluster to trust external services. Example: SQL Server CA Certificate, SMTP Server CA Certificate, etc.

Updating Cluster Certificates

The installation bundle provides a cluster management tool that enables you to update certificates post-installation.

To access it, navigate to the location of the installer bundle:

cd /opt/UiPathAutomationSuite/

For instructions on updating the certificates, see .

Accessing a cluster that uses self-signed certificates

If you are using a self-signed certificate, take the following steps to access the cluster:

You need to add CA (Certificate Authority) Bundle certificate to the trust store for the following:

• Client machine
  • Machine on which robot will run.
  • Machine on which you will access Automation Suite from the browser.
• First server machine (requirement for air-gapped)
  • Machine on which air-gapped bundle will be downloaded and extracted.

Use the following command to add the certificate to the trust store of the RHEL machine.

sudo cp --remove-destination rootCA.crt /etc/pki/ca-trust/source/anchors/
sudo update-ca-trust