- 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: Migrating standalone Test Manager
- Step 9: 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
- Velero backup fails with FailedValidation error
- Accessing FQDN returns RBAC access denied error

Automation Suite on EKS/AKS installation guide
Compatibility matrix
Azure third-party component compatibility
The following table lists the third-party software compatible with the latest version of Automation Suite on AKS.
| Prerequisites for Azure | Compatible versions |
|---|---|
| Azure Kubernetes Service (AKS) Architecture | x86 |
| Ubuntu | 22.04 |
| Cloud Redis | Version 6 |
| Microsoft SQL Server | Microsoft SQL Server 2016, 2017, 2019 and 2022, Standard and Enterprise editions. For product-specific version dependency, see SQL database . |
| PostgreSQL (for Process Mining Airflow database)
Process Mining on Automation Suite 2023.10.9 or higher. | PostgreSQL 12.x to 16.x are supported. It is recommended to use the most recent version of PostgreSQL within this range for optimal compatibility and performance. |
| Prometheus (if you bring your own) | 3.5.0 |
| Grafana (if you bring your own) | 12.0.2 |
| Alert Manager (if you bring your own) | 0.28.1 |
| FluentD/Fluent-bit (if you bring your own) helm-charts: logging-operator, logging-operator-logging | 6.0.1 |
| Gatekeeper (if you bring your own) helm-charts : gatekeeper | 3.20.0 |
| Velero (if you bring your own) helm-charts : velero | 10.0.10 |
| Cert Manager (if you bring your own) helm-charts : cert-manager | 1.18.2 |
| Istio (if you bring your own) helm-charts : istio-base | 1.26.3 |
AWS third-party component compatibility
The following table lists the third-party software compatible with the latest version of Automation Suite on EKS.
| Prerequisites for AWS | Compatible versions |
|---|---|
| Elastic Kubernetes Service (EKS) Architecture | x86 |
| RHEL | 8.8 for EKS 1.33 |
| Amazon Linux | AL2 and AL2023 for all EKS versions except EKS 1.33 where only AL2023 is supported |
| Bottlerocket | 1.19.2 |
| Elasticache | version 6.2.6 |
| Database - RDS | 15.00.4236.7.v1 |
| Prometheus (if you bring your own) | 3.5.0 |
| Grafana (if you bring your own) | 12.0.2 |
| Alert Manager (if you bring your own) | 0.28.1 |
| FluentD/Fluent-bit (if you bring your own) helm-charts: logging-operator, logging-operator-logging | 6.0.1 |
| Gatekeeper (if you bring your own) helm-charts: gatekeeper | 3.20.0 |
| Velero (if you bring your own) helm-charts: velero | 10.0.10 |
| Cert Manager (if you bring your own) helm-charts: cert-manager | 1.18.2 |
| Istio (if you bring your own) helm-charts: istio-base | 1.26.3 |
Kubernetes compatibility
To receive UiPath® support for a particular Automation Suite Cumulative Update (CU), you must use both an Automation Suite version and a Kubernetes version that are currently supported.
The support calendar for Automation Suite is available in the Product lifecycle section of the Overview guide. For the Kubernetes support calendar, see the Kubernetes documentation.
Updating your Kubernetes cluster to a supported version may require updating Automation Suite to a newer CU. For example, if you are on Automation Suite 2023.10.0, the last supported version for your cluster is Kubernetes 1.27. As this version reached its end of life, you must update your cluster to a newer Kubernetes version. This also requires updating to a newer Automation Suite CU.
The following table lists the Kubernetes versions compatible with each Automation Suite 2023.10.x CU.
| Automation Suite version | Compatible Kubernetes versions |
|---|---|
| 2023.10.12 | 1.31, 1.32, 1.33 |
| 2023.10.11 | 1.31, 1.32, 1.33 |
| 2023.10.10 | 1.30, 1.31, 1.32 |
| 2023.10.9 | 1.30, 1.31, 1.32 |
| 2023.10.8 | 1.29 , 1.30, 1.31 |
| 2023.10.7 | 1.29, 1.30, 1.31 |
| 2023.10.6 | 1.28, 1.29, 1.30 |
| 2023.10.5 | 1.28, 1.29, 1.30 |
| 2023.10.4 | 1.28, 1.29, 1.30 |
| 2023.10.3 | 1.27, 1.28, 1.29 |
| 2023.10.2* | 1.26, 1.27, 1.28 |
| 2023.10.1* | 1.25, 1.26, 1.27 |
| 2023.10.0* | 1.25, 1.26, 1.27 |
The Automation Suite versions marked with an asterisk () are out of support due to all the compatible Kubernetes versions also being out of support.