- Overview
- Requirements
- Pre-installation
- Installation
- Post-installation
- Migration and upgrade
- Upgrading Automation Suite
- Migrating standalone products to Automation Suite
- Step 1: Restoring the standalone product database
- Step 2: Updating the schema of the restored product database
- Step 3: Moving the Identity organization data from standalone to Automation Suite
- Step 4: Backing up the platform database in Automation Suite
- Step 5: Merging organizations in Automation Suite
- Step 6: Updating the migrated product connection strings
- Step 7: Migrating standalone Orchestrator
- Step 8: Migrating standalone Insights
- Step 9: Deleting the default tenant
- Performing a single tenant migration
- Migrating between Automation Suite clusters
- Migrating from Automation Suite on EKS/AKS to Automation Suite on OpenShift
- Monitoring and alerting
- Cluster administration
- Performing database maintenance
- Configuring the FQDN post-installation
- Forwarding logs to external tools
- Switching to the secondary cluster manually in an Active/Passive setup
- Converting an existing installation to multi-site setup
- Guidelines on upgrading an Active/Passive deployment
- Guidelines on backing up and restoring an Active/Passive deployment
- Product-specific configuration
- Troubleshooting
- The backup setup does not work due to a failure to connect to Azure Government
- Pods in the uipath namespace stuck when enabling custom node taints
- Unable to launch Automation Hub and Apps with proxy setup
- Robot cannot connect to an Automation Suite Orchestrator instance
- Log streaming does not work in proxy setups
Automation Suite on EKS/AKS installation guide
If you exited the Automation Suite setup, you can convert that into multi-site by taking the following steps:
-
Convert the standalone Automation Suite cluster into the primary cluster. For details, see the following section.
-
Install secondary Automation Suite cluster. For details, see Disaster Recovery - Installing the secondary cluster.
To convert an existing Automation Suite cluster into a primary cluster of the multi-site deployment, take the following steps:
-
Update
input.json. -
Configure the infrastructure on the first server node.
-
Configure the fabric and services on the first server node.
Updating input.json
Add or modify the required input.json parameters on the first server node.
For more details, see the following documentation: Advanced installation
experience
It is recommended to keep the FQDN of your existing Automation Suite setup to avoid reconfiguring all your robots.
Configuring the services and reapplying the manifests
To configure the services and reapply the manifests, run the following command:
uipathctl manifest apply input.json --versions version.jsonuipathctl manifest apply input.json --versions version.json
