- 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
Orchestrator supports the following storage configurations:
- Cluster-level storage configuration;
- Orchestrator-level storage configuration.
We recommend using the cluster-level configuration paired with external storage. This allows Orchestrator to automatically detect and use the settings, eliminating the need for additional configuration.
To configure the Orchestrator-level storage provider, update the Orchestrator parameters by taking the following steps. For more details, see Configuring the Orchestrator parameters.
-
In the configuration file, under
orchestrator, add thelegacy_storage_providersection that contains the storage type and connection string, as shown in the following example:"orchestrator": { "enabled": true, "legacy_object_storage": { "type": "Azure", "connection_string": "DefaultEndpointsProtocol=https;AccountName=usr;AccountKey=...;EndpointSuffix=core.windows.net" } }"orchestrator": { "enabled": true, "legacy_object_storage": { "type": "Azure", "connection_string": "DefaultEndpointsProtocol=https;AccountName=usr;AccountKey=...;EndpointSuffix=core.windows.net" } } - Set the desired provider using the
typeparameter. The possible values are:Azure,AWS, andMinio. A few considerations:- The
storage.typeparameter values are case-sensitive; - FileSystem storage configuration is not supported.
- The
- Add the connection string for the storage provider using the
connection_stringparameter. For details on the connection strings format, see theStorage.Locationsection of UiPath.Orchestrator.dll.config.
Orchestrator web browser access to Amazon and Azure storage buckets could be restricted due to the same-origin policy on the provider side. To successfully access the content of such a bucket, you must configure the respective provider to allow cross-origin requests from Orchestrator. For instructions, see CORP/CSP configuration.
To use network FileStore, edit the following Orchestrator ArgoCD app parameters:
storage.type = smbstorage.smb.domainstorage.smb.passwordstorage.smb.sourcestorage.smb.usernamestorage.smb.size
When Orchestrator uses cluster-level storage configuration, files can be uploaded to the storage using the Orchestrator Configurator Tool. To do that, use the following command:
./orchestrator_configurator.sh -s path./orchestrator_configurator.sh -s pathThe subfolders from the path will be uploaded to the configured storage.
--use-external-storage flag.
