- Overview
- Requirements
- Root privileges requirements
- High Availability – three availability zones
- Certificate Requirements
- Network Requirements
- Validating the Prerequisites in a Single-node Evaluation Setup
- Validating the Prerequisites in a Multi-node HA-ready Production Setup
- Installation
- Post-installation
- Cluster administration
- Managing products
- Managing the cluster in ArgoCD
- Setting up the external NFS server
- Automated: Enabling the Backup on the Cluster
- Automated: Disabling the Backup on the Cluster
- Automated, Online: Restoring the Cluster
- Automated, Offline: Restoring the Cluster
- Manual: Enabling the Backup on the Cluster
- Manual: Disabling the Backup on the Cluster
- Manual, Online: Restoring the Cluster
- Manual, Offline: Restoring the Cluster
- Additional configuration
- Migrating objectstore from persistent volume to raw disks
- Monitoring and alerting
- Migration and upgrade
- Migration options
- Step 1: Moving the Identity organization data from standalone to Automation Suite
- Step 2: Restoring the standalone product database
- Step 3: Backing up the platform database in Automation Suite
- Step 4: Merging organizations in Automation Suite
- Step 5: Updating the migrated product connection strings
- Step 6: Migrating standalone Insights
- Step 7: Deleting the default tenant
- B) Single tenant migration
- Product-specific configuration
- Best practices and maintenance
- Troubleshooting
- How to Troubleshoot Services During Installation
- How to Uninstall the Cluster
- How to clean up offline artifacts to improve disk space
- How to clear Redis data
- How to enable Istio logging
- How to manually clean up logs
- How to clean up old logs stored in the sf-logs bucket
- How to disable streaming logs for AI Center
- How to debug failed Automation Suite installations
- How to delete images from the old installer after upgrade
- How to automatically clean up Longhorn snapshots
- How to disable TX checksum offloading
- How to address weak ciphers in TLS 1.2
- Unable to run an offline installation on RHEL 8.4 OS
- Error in Downloading the Bundle
- Offline installation fails because of missing binary
- Certificate issue in offline installation
- First installation fails during Longhorn setup
- SQL connection string validation error
- Prerequisite check for selinux iscsid module fails
- Azure disk not marked as SSD
- Failure After Certificate Update
- Automation Suite not working after OS upgrade
- Automation Suite Requires Backlog_wait_time to Be Set 1
- Volume unable to mount due to not being ready for workloads
- RKE2 fails during installation and upgrade
- Failure to upload or download data in objectstore
- PVC resize does not heal Ceph
- Failure to Resize Objectstore PVC
- Rook Ceph or Looker pod stuck in Init state
- StatefulSet volume attachment error
- Failure to create persistent volumes
- Storage reclamation patch
- Backup failed due to TooManySnapshots error
- All Longhorn replicas are faulted
- Setting a timeout interval for the management portals
- Update the underlying directory connections
- Cannot Log in After Migration
- Kinit: Cannot Find KDC for Realm <AD Domain> While Getting Initial Credentials
- Kinit: Keytab Contains No Suitable Keys for *** While Getting Initial Credentials
- GSSAPI Operation Failed With Error: An Invalid Status Code Was Supplied (Client's Credentials Have Been Revoked).
- Alarm Received for Failed Kerberos-tgt-update Job
- SSPI Provider: Server Not Found in Kerberos Database
- Login Failed for User <ADDOMAIN><aduser>. Reason: The Account Is Disabled.
- ArgoCD login failed
- Failure to get the sandbox image
- Pods not showing in ArgoCD UI
- Redis Probe Failure
- RKE2 Server Fails to Start
- Secret Not Found in UiPath Namespace
- After the Initial Install, ArgoCD App Went Into Progressing State
- MongoDB pods in CrashLoopBackOff or pending PVC provisioning after deletion
- Unexpected Inconsistency; Run Fsck Manually
- Degraded MongoDB or Business Applications After Cluster Restore
- Missing Self-heal-operator and Sf-k8-utils Repo
- Unhealthy Services After Cluster Restore or Rollback
- RabbitMQ pod stuck in CrashLoopBackOff
- Prometheus in CrashloopBackoff state with out-of-memory (OOM) error
- Missing Ceph-rook metrics from monitoring dashboards
- Pods cannot communicate with FQDN in a proxy environment
- Using the Automation Suite Diagnostics Tool
- Using the Automation Suite support bundle
- Exploring Logs

Automation Suite installation guide
Validating the Prerequisites in a Multi-node HA-ready Production Setup
Before installing Automation Suite, it is good practice to validate the installation prerequisites and infrastructure readiness. You can use the dedicated script to evaluate your environment and generate a summary before performing the installation.
sf-installer.zip
, and supporting tools are bundled as sf-infra.tar.gz
for offline only. You need these files to generate a report on all the machines on which you plan to install Automation Suite.
Installation type |
Files to download |
---|---|
Online |
sf-installer.zip – Mandatory. For download instructions, see sf-installer.zip.
|
Offline |
sf-installer.zip – Mandatory. For download instructions, see sf-installer.zip.
sf-infra.tar.gz – Mandatory. For download instructions, see sf-infra.tar.gz.
|
-
Become root by running the following command:
sudo su -
sudo su - -
Copy the files to the
/opt/UiPathAutomationSuite/{version}
folder by running the following command:VERSION="" #add the version number you are trying to install. Ex: for 2022.4.0 Set VERSION="2022.4.0" mkdir -p /opt/UiPathAutomationSuite/${VERSION} # For below command replace the /path/to where actually the files are present. cp /path/to/sf-installer.zip /opt/UiPathAutomationSuite/${VERSION} # Additionally for offline, copy sf-infra.tar.gz as well to /opt/UiPathAutomationSuite/{VERSION} folder cp /path/to/sf-infra.tar.gz /opt/UiPathAutomationSuite/${VERSION} cd /opt/UiPathAutomationSuite/${VERSION}
VERSION="" #add the version number you are trying to install. Ex: for 2022.4.0 Set VERSION="2022.4.0" mkdir -p /opt/UiPathAutomationSuite/${VERSION} # For below command replace the /path/to where actually the files are present. cp /path/to/sf-installer.zip /opt/UiPathAutomationSuite/${VERSION} # Additionally for offline, copy sf-infra.tar.gz as well to /opt/UiPathAutomationSuite/{VERSION} folder cp /path/to/sf-infra.tar.gz /opt/UiPathAutomationSuite/${VERSION} cd /opt/UiPathAutomationSuite/${VERSION} -
Unzip the package by running the following command:
unzip sf-installer.zip -d installer
unzip sf-installer.zip -d installer -
Assign the necessary permissions and navigate to the script folder by running the following command:
chmod -R 755 installer cd installer
chmod -R 755 installer cd installer
To view the help section and supported flags, run the following command:
./validateUiPathASReadiness.sh --help
./validateUiPathASReadiness.sh --help
Output:
***************************************************************************************
validateUiPathASReadiness.sh Runs pre-install validation checks
Arguments:
-i|--input Specify cluster config json file
-m|--machines Comma separated IP address / hostnames of all the machines
-n|--node-type Possible values [server|agent|task-mining|gpu]. Defaults to server
--install-type Possible values [online|offline]. Defaults to online
--install-standalone-aicenter Run checks for standalone aicenter service only
--prereq-bundle </uipath/sf-infra.tar.gz> Specify the path to the prereq bundle, only for offline installation
--prereq-tmp-folder </uipath> Specify parent directory for the temporary install folder, only for offline installation
-h|--help Display help
***************************************************************************************
***************************************************************************************
validateUiPathASReadiness.sh Runs pre-install validation checks
Arguments:
-i|--input Specify cluster config json file
-m|--machines Comma separated IP address / hostnames of all the machines
-n|--node-type Possible values [server|agent|task-mining|gpu]. Defaults to server
--install-type Possible values [online|offline]. Defaults to online
--install-standalone-aicenter Run checks for standalone aicenter service only
--prereq-bundle </uipath/sf-infra.tar.gz> Specify the path to the prereq bundle, only for offline installation
--prereq-tmp-folder </uipath> Specify parent directory for the temporary install folder, only for offline installation
-h|--help Display help
***************************************************************************************
The following table describes the parameters you can use when running the script:
Parameter |
Description |
---|---|
|
Accepts the
cluster_config.json file as input. This file defines the parameters, settings, and preferences applied to the UiPath services deployed via Automation
Suite. For details, see Advanced Installation Experience.
If you do not provide this file, the script will trigger the interactive experience to collect these inputs. The file will then be generated on your behalf. |
|
Accepts comma-separated IP address / hostnames of all the machines. This is required to check the connectivity between all the nodes on the required port. The parameter is mandatory for multi-node HA-ready production installations. In addition to that, the parameter is also required if you plan to add a Task Mining or GPU node in a single-node evaluation cluster. |
|
Accepts the type of the current node. Possible values are:
server , agent , task-mining , and gpu .
The default value is
server .
|
|
Accepts the installation method:
online or offline .
The default value is
online .
|
|
This is a Boolean flag. Pass it if you plan to install standalone AI Center. |
|
Accepts the absolute path where the
sf-infra.tar.gz is located.
|
|
Accepts the absolute path where
sf-infra.tar.gz bundle will be temporarily extracted. If this path is not provided, the installer will select the /tmp folder.
|
- To validate the first server machine, run the following command:
Online
./validateUiPathASReadiness.sh \
--node-type server \
--install-type online \
--machines "10.0.1.8, 10.0.1.9" #replace with actual machine IPs of all the nodes in cluster
./validateUiPathASReadiness.sh \
--node-type server \
--install-type online \
--machines "10.0.1.8, 10.0.1.9" #replace with actual machine IPs of all the nodes in cluster
Offline
./validateUiPathASReadiness.sh \
--node-type server \
--install-type offline \
--prereq-bundle ../sf-infra.tar.gz \
--prereq-tmp-folder /opt/UiPathAutomationSuite/tmp \
--machines "10.0.1.8, 10.0.1.9" #replace with actual machine IPs of all the nodes in cluster
./validateUiPathASReadiness.sh \
--node-type server \
--install-type offline \
--prereq-bundle ../sf-infra.tar.gz \
--prereq-tmp-folder /opt/UiPathAutomationSuite/tmp \
--machines "10.0.1.8, 10.0.1.9" #replace with actual machine IPs of all the nodes in cluster
cluster_config.json
file under the /opt/UiPathAutomationSuite
folder. This file is required on all the other machines.
cluster_config.json
file on the other machines, run the following command:
scp /opt/UiPathAutomationSuite/cluster_config.json <username>@<node dns>:/opt/UiPathAutomationSuite
scp /opt/UiPathAutomationSuite/cluster_config.json <username>@<node dns>:/opt/UiPathAutomationSuite
/opt/UiPathAutomationSuite
folder due to permission errors, you can temporarily copy it to /var/tmp
on the new machines, and then move it to /opt/UiPathAutomationSuite
.
777
) to the /opt/UiPathAutomationSuite
folder on the new machines, by running the following command: chmod -R 777 /opt/UiPathAutomationSuite
.
To validate the other server machines, run the following command:
Online
./validateUiPathASReadiness.sh \
--input /opt/UiPathAutomationSuite/cluster_config.json \
--node-type server \
--install-type online \
--machines "10.0.1.8, 10.0.1.9" #replace with actual machine IP of all the nodes in cluster
./validateUiPathASReadiness.sh \
--input /opt/UiPathAutomationSuite/cluster_config.json \
--node-type server \
--install-type online \
--machines "10.0.1.8, 10.0.1.9" #replace with actual machine IP of all the nodes in cluster
Offline
./validateUiPathASReadiness.sh \
--input /opt/UiPathAutomationSuite/cluster_config.json \
--node-type server \
--install-type offline \
--prereq-bundle ../sf-infra.tar.gz \
--prereq-tmp-folder /opt/UiPathAutomationSuite/tmp \
--machines "10.0.1.8, 10.0.1.9" #replace with actual machine IP of all the nodes in cluster
./validateUiPathASReadiness.sh \
--input /opt/UiPathAutomationSuite/cluster_config.json \
--node-type server \
--install-type offline \
--prereq-bundle ../sf-infra.tar.gz \
--prereq-tmp-folder /opt/UiPathAutomationSuite/tmp \
--machines "10.0.1.8, 10.0.1.9" #replace with actual machine IP of all the nodes in cluster
To validate the agent machines, run the following command:
Online
./validateUiPathASReadiness.sh \
--input /opt/UiPathAutomationSuite/cluster_config.json \
--node-type agent \
--install-type online \
--machines "10.0.1.8, 10.0.1.9" # replace with actual machine IP of all the nodes in cluster
./validateUiPathASReadiness.sh \
--input /opt/UiPathAutomationSuite/cluster_config.json \
--node-type agent \
--install-type online \
--machines "10.0.1.8, 10.0.1.9" # replace with actual machine IP of all the nodes in cluster
Offline
./validateUiPathASReadiness.sh \
--input /opt/UiPathAutomationSuite/cluster_config.json \
--node-type agent \
--install-type offline \ #replace with offline for airgap
--prereq-bundle ../sf-infra.tar.gz \
--prereq-tmp-folder /opt/UiPathAutomationSuite/tmp \
--machines "10.0.1.8, 10.0.1.9" # replace with actual machine IP of all the nodes in cluster
./validateUiPathASReadiness.sh \
--input /opt/UiPathAutomationSuite/cluster_config.json \
--node-type agent \
--install-type offline \ #replace with offline for airgap
--prereq-bundle ../sf-infra.tar.gz \
--prereq-tmp-folder /opt/UiPathAutomationSuite/tmp \
--machines "10.0.1.8, 10.0.1.9" # replace with actual machine IP of all the nodes in cluster
To validate the Task Mining & GPU machines, run the following command:
--node-type task-mining
and --node-type gpu
, respectively, in the following commands.
Online
./validateUiPathASReadiness.sh \)\)
--input /opt/UiPathAutomationSuite/cluster_config.json \)\)
--node-type task-mining \)\) #replace with GPU for GPU node
--install-type online \)\)
--machines "10.0.1.8, 10.0.1.9" # replace with actual machine IP of all the nodes in cluster
./validateUiPathASReadiness.sh \)\)
--input /opt/UiPathAutomationSuite/cluster_config.json \)\)
--node-type task-mining \)\) #replace with GPU for GPU node
--install-type online \)\)
--machines "10.0.1.8, 10.0.1.9" # replace with actual machine IP of all the nodes in cluster
Offline
./validateUiPathASReadiness.sh \)\)
--input /opt/UiPathAutomationSuite/cluster_config.json \)\)
--node-type task-mining \)\) #replace with GPU for GPU node
--install-type offline \)\)
--prereq-bundle ../sf-infra.tar.gz \)\)
--prereq-tmp-folder /opt/UiPathAutomationSuite/tmp \)\)
--machines "10.0.1.8, 10.0.1.9" # replace with actual machine IP of all the nodes in cluster
./validateUiPathASReadiness.sh \)\)
--input /opt/UiPathAutomationSuite/cluster_config.json \)\)
--node-type task-mining \)\) #replace with GPU for GPU node
--install-type offline \)\)
--prereq-bundle ../sf-infra.tar.gz \)\)
--prereq-tmp-folder /opt/UiPathAutomationSuite/tmp \)\)
--machines "10.0.1.8, 10.0.1.9" # replace with actual machine IP of all the nodes in cluster