- Overview
- Requirements
- Installation
- Q&A: Deployment templates
- Downloading the installation packages
- Install-uipath.sh Parameters
- Enabling Redis High Availability Add-On for the cluster
- Document Understanding configuration file
- Adding a dedicated agent node with GPU support
- Connecting Task Mining application
- Adding a dedicated agent Node for Task Mining
- Adding a Dedicated Agent Node for Automation Suite Robots
- Post-installation
- Cluster administration
- 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
- Performing a 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
- Antivirus causes installation issues
- Automation Suite not working after OS upgrade
- Automation Suite requires backlog_wait_time to be set to 0
- Volume unable to mount due to not being ready for workloads
- Unable to launch Automation Hub and Apps with proxy setup
- Failure to upload or download data in objectstore
- PVC resize does not heal Ceph
- Failure to resize PVC
- 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
- Authentication not working 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 due to invalid status code
- Alarm received for failed Kerberos-tgt-update job
- SSPI provider: Server not found in Kerberos database
- Login failed for AD user due to disabled account
- 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
- ArgoCD goes into progressing state after first installation
- Unexpected inconsistency; run fsck manually
- MongoDB pods in CrashLoopBackOff or pending PVC provisioning after deletion
- MongoDB Pod Fails to Upgrade From 4.4.4-ent to 5.0.7-ent
- Unhealthy services after cluster restore or rollback
- Pods stuck in Init:0/X
- 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
Step 1.1: Creating the VM
linkCreating a Resource Group
linkYou need to have a resource group under your Azure subscription for running Automation Suite. If you want to use an existing one, you can skip this step and specify the resource group in the later steps.
- Go to the Azure portal.
- If you create a new one, then select Resource Group from the home page and select Create.
Creating a Virtual Network Under the Same Resource Group
link- Go to the Azure portal.
- Search for Virtual Network from the home page and select Create.
All the machines that we provision should be part of this virtual network
Creating a Network Security Group
link- Go to the Azure portal.
- Create a Network security group under the target resource group.
All the machines that we provision should make use of this common network security group.
- Search for Network Security Group from the home page and select Create.
The Network Security Group should be under the Resource Group.
Creating a Virtual Machine
link- Go to the Azure portal.
- Type virtual machines in the search field.
- Under Services, select Virtual machines.
- In the Virtual machines page, select Create. The Create a virtual machine page opens.
Basics Tab
- In the Basics tab, under Project details, make sure the correct subscription is selected and then choose to Create new resource group (or select an existing from the list). Type for the name.
- Under Instance details, set your VM name for the Virtual machine name, choose your Region, and choose Red Hat Enterprise Linux OS 8.2 or higher for your Image. Leave the other defaults.
- Please see the hardware requirements for machine size based on the products installed.
- For example, a single-node evaluation deployment VM for the basic selection of products can be
Standard_D16s_v3
, and for the complete selection,Standard_D32s_v3
. Please choose the appropriate size from the drop-down list. You can find those machines in theD-Series v3
option in the drop-downs.Note: If you search for Standard_D32s_v3 to find the machine size, no results are returned. You need to search for D32s_v3 instead. - For a multi-node HA-ready production deployment - for the basic selection of products you can select 3 x
Standard_D16s_v3
, and for the complete selection, 3 xStandard_D32s_v3
or 6 xStandard_D16s_v3
. Please choose the appropriate size from the drop-down list. - If you want GPU support, then you need to select NC type VMs,
Standard_NC12
orStandard_NC12s_v2
. The rest of the steps are same for these VMs.
- For example, a single-node evaluation deployment VM for the basic selection of products can be
- Under Administrator account, select Password authentication type, and fill in the rest of the fields.
- Inbound port rules. Select HTTPS (
443
) and SSH (22
) ports. - From here, you can go to Next: Disks >.
Adding Secondary Disk Drives
linkYou can configure the VM directly during the creation step under the Disks tab.
- Make sure you have the following disks and that they meet the requirements:
Disk label
Size
Cluster disk
256 GB SSD and Min IOPS: 1100
etcd disk
16 GB SSD and Min IOPS: 240
Data disk
Basic installation: 512 GB SSD and Min IOPS: 1100
Complete installation: 2 TB SSD and Min IOPS: 1100
UiPath® bundle disk
512 GB SSD and Min IOPS: 1100
Note:Data and etcd disks should be separate physical disks. This physically isolates the data and etcd disks from other cluster workload and activity while also enhancing the performance and stability of the cluster.
The UiPath® bundle disk is only required for offline installations.
- Select Create and attach a new disk.
Networking
linkFollow these steps to create a new Virtual Network (or select the existing one) and Public IP address:
- You can select the Virtual Network created at the previous step or select Create New under the Virtual Network drop-down to provide a name and Save. Do not select other checkboxes.Important: Make sure that any additional nodes that you configure are added to the same Virtual Network selected here.
- Select Create New under Public IP drop-down.
- Please choose the Standard SKU from Public IP:
- Press Review and Create and then Create.
- If you create the machine, wait until you see the following screen to indicate a complete deployment:
- Select "Go to Resource" and proceed to the next step.