- 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
- Disaster Recovery: Performing post-installation operations
- 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

Automation Suite on EKS/AKS installation guide
Upgrading Automation Suite
Automation Suite consists of multiple components. Both you as a customer and UiPath® share responsibility of these components. For details, see Responsibility matrix.
You are responsible for upgrading:
- Kubernetes infrastructure where Automation Suite is deployed (AKS or EKS)
- Components that you choose to bring as part of Automation Suite (e.g., Gatekeeper, FluentD, etc.)
UiPath® is responsible for upgrading:
- UiPath® services (e.g., Orchestrator)
- Components deployed as part of Automation Suite (e.g., ArgoCD)
If you upgrade to Automation Suite 2024.10 and want to use Document Understanding modern projects, you must meet the additional hardware requirements we specify in Additional Document Understanding recommendations.
AutomationSuite_Airflow
and configure the connection string for it in input.json
.
Refer to Process Mining-specific configuration for details.
There is a known issue with the backup logic in Automation Suite for AKS/EKS versions 2024.10.0 to 2024.10.1. Specifically, this issue excludes the backup of Insights dashboards and Studio Web data. However, all historical data is successfully backed up.
You are responsible for upgrading the Kubernetes infrastructure hosting Automation Suite. You should follow the standard practices of your company to upgrade Kubernetes infrastructure.