automation-suite
2024.10
false
- Overview
- Requirements
- Pre-installation
- Preparing the installation
- Installing and configuring the service mesh
- Downloading the installation packages
- Configuring the OCI-compliant registry
- Granting installation permissions
- Installing and configuring the GitOps tool
- Deploying Redis through OperatorHub
- Applying miscellaneous configurations
- Running uipathctl
- 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: Migrating standalone Test Manager
- Step 10: Deleting the default tenant
- Performing a single tenant migration
- Migrating between Automation Suite clusters
- Monitoring and alerting
- Cluster administration
- Product-specific configuration
- Orchestrator advanced configuration
- Configuring Orchestrator parameters
- Configuring appSettings
- Configuring the maximum request size
- Overriding cluster-level storage configuration
- Configuring NLog
- Saving robot logs to Elasticsearch
- Configuring credential stores
- Configuring encryption key per tenant
- Cleaning up the Orchestrator database
- Skipping host library creation
- Troubleshooting
Automation Suite on OpenShift installation guide
Last updated Mar 26, 2026
ODF presigned URL limitation
Description
When using OpenShift Data Foundation (ODF) as the objectstore on OpenShift cluster versions < 4.19, CORS cannot be configured. This limitation can prevent Automation Suite services from working correctly with ODF buckets.
If you attempt to modify the presigned URL configuration after the initial installation, the installer blocks the change and shows the following error:
cannot change presigned url configuration after initial installation
cannot change presigned url configuration after initial installation
Solution
To address the issue, you must disable presigned URL usage globally by adding the following flag to your input.json file:
"disable_presigned_url": true
"disable_presigned_url": true
If the change occurs after installation and the installer prevents the update, take the following steps:
- Run the following command to locate the secret:
oc get secret service-cluster-configurations -n uipath -o yamloc get secret service-cluster-configurations -n uipath -o yaml - Update the
DISABLE_PRESIGNED_URLkey in the secret to the base64-encoded value of true (dHJ1ZQ==). - Add the following flag in your
input.jsonfile:"disable_presigned_url": true"disable_presigned_url": true - Re-run the installer.