automation-suite
2023.10
false
- Overview
- Requirements
- Installation
- Post-installation
- Migration and upgrade
- Upgrading Automation Suite on EKS/AKS
- 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 Orchestrator
- Step 7: Migrating standalone Insights
- Step 8: Deleting the default tenant
- Performing a single tenant migration
- Migrating from Automation Suite on Linux to Automation Suite on EKS/AKS
- Monitoring and alerting
- Cluster administration
- 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
- Pods cannot communicate with FQDN in a proxy environment
- Test Automation SQL connection string is ignored
- EKS backup failure due to Velero version

Automation Suite on EKS/AKS installation guide
Last updated Oct 24, 2025
An Automation Suite patch is an update to an existing version, which addresses bugs or security vulnerabilities. For instance, patch 2023.10.2+patch3 addresses issues impacting version 2023.10.2.
Important:
Instead of applying the patch, we recommend upgrading to the Cumulative Update (CU) that contains the same fix. All fixes provided in patches will also be available in the CU mentioned in the release notes for the patch.
To apply a patch to an existing Automation Suite version, take the following steps: