- Overview
- Requirements
- Deployment templates
- Manual: Preparing the installation
- Manual: Preparing the installation
- Step 2: Configuring the OCI-compliant registry for offline installations
- Step 3: Configuring the external objectstore
- Step 4: Configuring High Availability Add-on
- Step 5: Configuring SQL databases
- Step 7: Configuring the DNS
- Step 8: Configuring the disks
- Step 9: Configuring kernel and OS level settings
- Step 10: Configuring the node ports
- Step 11: Applying miscellaneous settings
- Step 12: Validating and installing the required RPM packages
- Step 13: Generating cluster_config.json
- Cluster_config.json Sample
- General configuration
- Profile configuration
- Certificate configuration
- Database configuration
- External Objectstore configuration
- Pre-signed URL configuration
- ArgoCD configuration
- Kerberos authentication configuration
- External OCI-compliant registry configuration
- Disaster recovery: Active/Passive and Active/Active configurations
- High Availability Add-on configuration
- Orchestrator-specific configuration
- Insights-specific configuration
- Process Mining-specific configuration
- Document Understanding-specific configuration
- Automation Suite Robots-specific configuration
- AI Center-specific configuration
- Monitoring configuration
- Optional: Configuring the proxy server
- Optional: Enabling resilience to zonal failures in a multi-node HA-ready production cluster
- Optional: Passing custom resolv.conf
- Optional: Increasing fault tolerance
- Adding a dedicated agent node with GPU support
- Adding a Dedicated Agent Node for Automation Suite Robots
- Step 15: Configuring the temporary Docker registry for offline installations
- Step 16: Validating the prerequisites for the installation
- Running uipathctl
- Manual: Performing the installation
- Post-installation
- Cluster administration
- Managing products
- Getting Started with the Cluster Administration portal
- Migrating Redis from in-cluster to external High Availability Add-on
- Migrating data between objectstores
- Migrating in-cluster objectstore to external objectstore
- Migrating from in-cluster registry to an external OCI-compliant registry
- Switching to the secondary cluster manually in an Active/Passive setup
- Disaster Recovery: Performing post-installation operations
- Converting an existing installation to multi-site setup
- Guidelines on upgrading an Active/Passive or Active/Active deployment
- Guidelines on backing up and restoring an Active/Passive or Active/Active deployment
- Scaling a single-node (evaluation) deployment to a multi-node (HA) deployment
- Monitoring and alerting
- Migration and upgrade
- Migrating between Automation Suite clusters
- Upgrading Automation Suite
- Downloading the installation packages and getting all the files on the first server node
- Retrieving the latest applied configuration from the cluster
- Updating the cluster configuration
- Configuring the OCI-compliant registry for offline installations
- Executing the upgrade
- Performing post-upgrade operations
- Product-specific configuration
- Best practices and maintenance
- Troubleshooting
- How to troubleshoot services during installation
- How to reduce permissions for an NFS backup directory
- 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 disable TX checksum offloading
- How to manually set the ArgoCD log level to Info
- How to expand AI Center storage
- How to generate the encoded pull_secret_value for external registries
- How to address weak ciphers in TLS 1.2
- How to check the TLS version
- How to work with certificates
- How to schedule Ceph backup and restore data
- How to collect DU usage data with in-cluster objectstore (Ceph)
- How to install RKE2 SELinux on air-gapped environments
- How to clean up old differential backups on an NFS server
- Error in downloading the bundle
- Offline installation fails because of missing binary
- Certificate issue in offline installation
- SQL connection string validation error
- 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
- Temporary registry installation fails on RHEL 8.9
- Frequent restart issue in uipath namespace deployments during offline installations
- DNS settings not honored by CoreDNS
- Upgrade fails due to unhealthy Ceph
- RKE2 not getting started due to space issue
- Upgrade fails due to classic objects in the Orchestrator database
- Ceph cluster found in a degraded state after side-by-side upgrade
- Service upgrade fails for Apps
- In-place upgrade timeouts
- Upgrade fails in offline environments
- snapshot-controller-crds pod in CrashLoopBackOff state after upgrade
- Upgrade fails due to overridden Insights PVC sizes
- Upgrade failure due to uppercase hostname
- Setting a timeout interval for the management portals
- 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
- Update the underlying directory connections
- 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
- Missing Ceph-rook metrics from monitoring dashboards
- Mismatch in reported errors during diagnostic health checks
- No healthy upstream issue
- Redis startup blocked by antivirus
- Running High Availability with Process Mining
- Process Mining ingestion failed when logged in using Kerberos
- Unable to connect to AutomationSuite_ProcessMining_Warehouse database using a pyodbc format connection string
- Airflow installation fails with sqlalchemy.exc.ArgumentError: Could not parse rfc1738 URL from string ''
- How to add an IP table rule to use SQL Server port 1433
- Automation Suite certificate is not trusted from the server where CData Sync is running
- Running the diagnostics tool
- Using the Automation Suite support bundle
- Exploring Logs
- Exploring summarized telemetry

Automation Suite on Linux installation guide
Step 3: Post-deployment steps
Checking the installation status
Due to the way in which the GCP Marketplace deployments work, it is not possible to wait until the installation scripts are finished. The deployment is completed after the infrastructure is successfully deployed.
To get the status of the installation, you must use SSH to connect to the first server node using the following steps:
-
Select the deployment name.

-
Get the suffix from one of the resources.

-
Filter the VM instances with the suffix and SSH in the server with the lowest private IP (generally
10.0.0.7).
-
View the prerequisite logs in the
/tmp/prereqs.logsfile by running the following command:cat /tmp/prereqs.logscat /tmp/prereqs.logsThe prerequisite log file is generated on each node, at the beginning of the installation. The log generation process takes a few minutes.
To continuously view the logs on screen, run the following command:
tail -f /tmp/prereqs.logstail -f /tmp/prereqs.logs -
Check the
kubernetes/infrastructureinstallation logs in the/opt/UiPathAutomationSuite/install.logsfile by running the following command:cat /opt/UiPathAutomationSuite/install.logs #for all logs tail -f /opt/UiPathAutomationSuite/install.logs #to follow the logscat /opt/UiPathAutomationSuite/install.logs #for all logs tail -f /opt/UiPathAutomationSuite/install.logs #to follow the logsThe logs cover the entire installation, and the log file is created on all the machines.
Updating certificates
The installation process generates self-signed certificates on your behalf. These certificates are compliant with FIPS 140-2 and will expire in 90 days. 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.
If you installed Automation Suite on a FIPS 140-2-enabled host and want to update the certificates, make sure they arecompatible with FIPS 140-2.
For instructions, see Managing certificates.
Enabling FIPS 140-2
After completing an Automation Suite installation using the GCP deployment template, you can enable FIPS 140-2 on your machines. For instructions, see Security and compliance.
Accessing the deployment outputs
You can find the deployment outputs in the Solution output section, as shown in the following image:

Output definitions
The outputs give you the necessary information for accessing the suite and the cluster.
The following table describes the values:
| Key | Description |
|---|---|
Fqdn | The fully qualified domain name provided for the installation. Make sure you use the same one when configuring the DNS. For instructions on how to configure the DNS, see Configuring the DNS. |
Lb Ip | The load balancer's IP address used for configuring the DNS. |
Bastion Ip | The IP address of the bastion VM needed to access the cluster via SSH. |
Deployment Id | The deployment ID included in the name of all the resources in a deployment. |
Db Credentials | The URL to the secret containing the credentials for the database. |
As Host Credentials | The URL to the secret containing the credentials for the Host organization in the Automation Suite portal. |
As Default Credentials | The URL to the secret containing the credentials for the Host organization in the Automation Suite portal. |
Argocd Credentials | The URL to the secret containing the credentials for the ArgoCD console used to manage the installed products. |
Dashboard Monitoring Url | The URL to dashboard (Grafana) monitoring tools: https://monitoring.${var.lb_fqdn}/dashboard |
Metrics Monitoring Url | The URL to metrics (Prometheus) monitoring tools: https://monitoring.${var.lb_fqdn}/metrics |
Alertmanager Monitoring Url | The URL to Alertmanager monitoring tools: https://monitoring.${var.lb_fqdn}/alertmanager |
Accessing the Cluster Administration portal
The Cluster Administration portal is a centralized location where you can find all the resources required to complete an Automation Suite installation and perform common post-installation operations. For details, see Getting started with the Cluster Administration portal.
To access the Cluster Administration portal, take the following step:
Go to the following URL: https://${CONFIG_CLUSTER_FQDN}/uipath-management.
You do not need any credentials to access the Cluster Administration portal.
Accessing the services
To access the services, you must have a DNS configured. For details, see Configuring the DNS.
Alternatively, you can follow the instructions in Configuring a client machine to access the cluster for testing purposes only.
If using a self-signed certificate, you may get an certificate error as shown in the following image.

Select Proceed to…, then update the cluster certificates as explained in Managing the certificates.
Accessing the Automation Suite portal
You can access the Automation Suite portal at https://<fqdn>. You can get the credentials via a secret available at:
As Host CredentialsURL for the Host organization;As Default CredentialsURL for the Default organization.
Accessing ArgoCD
You can access the ArgoCD console at https://alm.<fqdn>. You can get the credentials via a secret that can be found at the argocd_credentials URL.
Accessing the monitoring tools
To access the monitoring tools for the first time, log in as an admin with the following default credentials:
- Username: admin
- Password: to retrieve the password , run the following command:
kubectl get secrets/dex-static-credential -n uipath -o "jsonpath={.data['password']}" | base64 --decodekubectl get secrets/dex-static-credential -n uipath -o "jsonpath={.data['password']}" | base64 --decode
To update the default password used for Dex authentication while accessing the monitoring tools, take the following steps.
- Run the following command by replacing
newpasswordwith your new password:password="newpassword" password=$(echo -n $password | base64) kubectl patch secret dex-static-credential -n uipath --type='json' -p="[{'op': 'replace', 'path': '/data/password', 'value': '$password'}]"password="newpassword" password=$(echo -n $password | base64) kubectl patch secret dex-static-credential -n uipath --type='json' -p="[{'op': 'replace', 'path': '/data/password', 'value': '$password'}]" - Run the following command to update the password:
./bin/uipathctl manifest apply /opt/UiPathAutomationSuite/cluster_config.json --versions versions/helm-charts.json./bin/uipathctl manifest apply /opt/UiPathAutomationSuite/cluster_config.json --versions versions/helm-charts.json
Accessing the cluster
To access the cluster machines via SSH, make sure to configure and use SSH in the browser. For details, see Google documentation.
Editing the number of nodes
Use the GPC console to edit number of nodes (server or agent nodes) as follows:
-
In the Instance Group tab, search for the MIGs, and select on the one corresponding to the node type you want to modify.

-
Select Edit.

-
Modify the Number of instances field according to your needs, and select Save.

Removing the deployment
To remove the deployment, delete the solution on the Solution deployments page.
- Checking the installation status
- Updating certificates
- Enabling FIPS 140-2
- Accessing the deployment outputs
- Output definitions
- Accessing the Cluster Administration portal
- Accessing the services
- Accessing the Automation Suite portal
- Accessing ArgoCD
- Accessing the monitoring tools
- Accessing the cluster
- Editing the number of nodes
- Removing the deployment