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.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.
| Deployment profile | Prerequisites | Requirements | Configuration | Installation |
|---|---|---|---|---|
| Single-node evaluation profile | One Linux machine (RHEL 8.3, 8.4, 8.5, 8.6, 8.7)
|
Single-node evaluation machine requirements | Configuring the machines | |
|
Microsoft SQL Server requirements | Configuring Microsoft SQL Server | ||
| DNS | N/A | Configuring the DNS | ||
| TLS 1.2+ | Updating the TLS protocol | N/A | ||
| Trusted TLS, token-signing and SQL connection encryption certificates | N/A | Configuring the certificates | ||
| 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 |
Important!
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.
Hardware requirements
Complete product selection
If you opt for the single-node evaluation profile, you must meet the following hard requirements for the Complete product selection. If you want to check the hardware requirements for individual products, see Capacity planning.
General requirements
| Hardware | Minimum requirement |
|---|---|
| Processor | 32 (v-)CPU/cores |
| RAM | 64 GiB |
| Cluster binaries and state disk for each node | 256 GiB SSD Min IOPS: 1100 |
| Block storage | 512 GiB SSD Min IOPS: 1100 |
| etcd disk for server node | 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 |
| Objectstore* | 512 GiB SSD Min IOPS: 1100 |
If you install Automation Suite in single-node evaluation mode, and you do not have a machine with 32 (v-)CPU/cores and 64 GiB of RAM, you can bring machines with a minimum of 8 (v-)CPU/cores and 16 GiB of RAM. For more details, see Capacity calculator.
If you choose this option, follow the multi-node installation and configuration instructions.To install the Complete product selection in single-node evaluation mode, you can bring 1 server node and 4 agent nodes of 8(v-)CPU and 16GiB each.
It is recommended to bring external objectstore whenever possible. This helps in scaling the objectstore independently of the cluster, and brings additional stability. We support the following objectstore options:
- Azure storage account
- AWS S3 storage bucket
- S3 compatible storage bucket
Additional Task Mining requirements
Task Mining requires an additional agent node that must meet the following requirements:
| Hardware | Minimum requirement |
|---|---|
| Processor | 20 (v-)CPU/cores |
| RAM | 60 GiB |
| Cluster binaries and state disk | 256 GiB SSD Min IOPS: 1100 |
| Data disk | N/A |
Additional Automation Suite Robots recommendations
In single-node evaluation environments, an additional Automation Suite Robots node is optional.
The hardware requirements for the Automation Suite Robots node depend on the way you plan to use your resources. In addition to the additional agent node requirements, you also need a minimum of 10 GB to enable package caching.
The following sections describe the factors that impact the amount of hardware the Automation Suite Robots node requires.
Robot size
The following table describes the required CPU, memory, and storage for all robot sizes.
| Size | CPU | Memory | Storage |
|---|---|---|---|
| Small | 0.5 | 1 GB | 1 GB |
| Standard | 1 | 2 GB | 2 GB |
| Medium | 2 | 4 GB | 4 GB |
| Large | 6 | 10 GB | 10 GB |
Agent node size
The resources of the Automation Suite Robots agent node have an impact on the number of jobs that can be run concurrently. The reason is that the number of CPU cores and the amount of RAM capacity are divided by the CPU/memory requirements of the job.
For example, a node with 16 CPUs and 32 GB of RAM would be able to run any of the following:
- 32 Small jobs
- 16 Standard jobs
- 8 Medium jobs
- 2 Large jobs
Job sizes can be mixed, so at any given moment, the same node could run a combination of jobs, such as the following:
- 10 Small jobs (consuming 5 CPUs and 10 GB of memory)
- 4 Standard jobs (consuming 4 CPUs and 8 GB of memory)
- 3 Medium jobs (consuming 6 CPUs and 12 GB of memory)
Kubernetes resource consumption
Given that the node is part of a Kubernetes cluster, the Kubernetes agent present on the server (kubelet) consumes a small amount of resources. Based on our measurements, the kubelet consumes the following resources:
- 0.6 CPU
- 0.4 GB RAM
A node similar to the one previously described would actually have approximately 15.4 CPUs and 31.6 GB of RAM.
Additional Document Understanding recommendations
For increased performance, you can install Document Understanding on an additional agent node with GPU support. Note, however, that Document Understanding is fully functional without the GPU node. Actually, Document Understanding uses CPU VMs for all its classification and extraction tasks, while for OCR we strongly recommend the usage of a GPU VM. Here you can find more information about the CPU/GPU usage within the Document Understanding framework.
If you want to use an additional node with GPU support, you must meet the following requirements:
| Hardrware | Minimum requirement |
|---|---|
| Processor | 8 (v-)CPU/cores |
| RAM | 52 GiB |
| Cluster binaries and state disk | 256 GiB SSD Min IOPS: 1100 |
| Data disk | N/A |
| GPU RAM | 11 GiB |
For more details, see AI Center considerations.
Individual products
This section lists the minimum hardware requirements for a successful Automation Suite deployment. The minimum hardware requirements for your deployment are the sum of the requirements for the shared suite capabilities and the individual products you install.
Aside from meeting the minimum hardware requirements listed in this section, it is highly recommended to have a 20% buffer.
The following table lists the requirements for the shared suite capabilities:
| CPU | RAM | |
|---|---|---|
| Shared suite capabilities | 9.5 (v-)CPU | 16.4 GiB |
The following table lists the requirements for individual products:
| Product | CPU | RAM |
|---|---|---|
| Action Center | 0.7 (v-)CPU | 2.1 GiB |
| AI Center | 2 (v-)CPU | 6.5 GiB |
| Apps | 2.8 (v-)CPU | 7.2 GiB |
| Automation Hub | 0.5 (v-)CPU | 1.4 GiB |
| Automation Ops | 0.2 (v-)CPU | 0.7 GiB |
| Automation Suite Robots | 0.5 (v-)CPU | 0.7 GiB |
| Data Service | 0.2 (v-)CPU | 0.5 GiB |
| Document Understanding | 3.2 (v-)CPU | 4 GiB |
| Insights | 0.3 (v-)CPU | 1.7 GiB |
| Orchestrator | 1 (v-)CPU | 2.6 GiB |
| Process Mining | 2.2 (v-)CPU | 3 GiB |
| Task Mining | 4 (v-)CPU | 5 GiB |
| Test Manager | 0.5 (v-)CPU | 1 GiB |
RPM package requirements
Before starting the Automation Suite manual installation, you must ensure you meet the following requirements:
- you have a RHEL subscription;
- you enabled the BaseOS and AppStream repositories;
- you installed the required RPM packages (you are responsible for installing the required RPM packages).
If you upgrade from a previous Automation Suite version, you have already installed the RPM packages.
The following table lists the required RPM packages:
| RPM package | Description |
|---|---|
iscsi-initiator-utils nfs-utils rpcbind util-linux nmap-ncat openssl httpd-tools gettext zstd | Required on nodes for installation. |
podman>=3.2.3 nmap-ncat bind-utils openssl wget unzip conmon=>2.0.24 | Required on nodes for the execution of the readiness check. |
ansible zip unzip | Required on the orchestration node for the execution of the uipathctl.sh functionality requiring Ansible. |
iscsi-initiator-utils gettext nfs-utils rpcbind util-linux nmap-ncat openssl httpd-tools podman=>3.2.3 zstd | Required for offline installations only. |
RHEL 8.3 includes Podman 1.6 by default, which may cause installation issues. To prevent this, update Podman to version 3.2.3.
RHEL 8.4 and later have the required RPM packages in the BaseOS and AppStream repositories by default.
For details on how to install the required RPM packages, see Configuring the machines.
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, and 2019 Standard and Enterprise editions are supported.
The minimum hardware requirements for Microsoft SQL Server are:
- 8 (v-)CPU
- 32 GiB RAM
- 256 GiB SSD
Updated 7 days ago