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 13, 2025
Standalone Orchestrator settings are stored in the
UiPath.Ochestrator.dll.config file. For a complete list of standalone Orchestrator settings, see UiPath.Orchestrator.dll.config.
Note that some of these settings are not available in Automation Suite for one of the following reasons:
- The related feature is no longer supported (e.g.
DefaultFolderIsClassic); - The setting is managed at cluster level, and modifying it could disrupt the integration of Orchestrator with other services
(e.g.
LoadBalancer.UseRedis); - There is another way to change that setting, such as via ArgoCD parameters.
The following table lists the parameters that were initially available in
UiPath.Orchestrator.dll.config file but that you cannot or must not change in Automation Suite:
|
Area |
Settings you must not change |
Alternative configuration |
|---|---|---|
|
Storage |
| We strongly recommend using the cluster-level storage configuration. This allows Orchestrator to be automatically configured. For more advanced storage configuration, see Overriding cluster-level storage configuration. |
|
Credential stores |
| Changing Plugins.SecureStores.Path can break the custom credential store plugins. To configure credential stores plugins, see Configuring credential stores.
|
| ||
| Encryption key |
| To migrate EncryptionKey from an existing Orchestrator, see Migrating Orchestrator.
|
|
Robot logs |
| To configure robot logs, see Saving robot logs to elasticsearch. |
|
Azure key vault |
| To configure EncryptionKeyPerTenant.Enabled and EncryptionKeyPerTenant.KeyProvider, see Configuring encryption key per tenant.
|
|
Identity Server |
|
N/A |
|
Authentication |
| N/A |
| ||
| ||
|
Load balancer |
| N/A |
|
Miscellaneous |
| N/A |
