automation-suite
2024.10
true
- 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
- Product-specific configuration
- Troubleshooting
Automation Suite on EKS/AKS installation guide
Last updated May 6, 2025
Configuring credential stores
The following secure stores are already available in Orchestrator:
- Azure Key Vault
- CyberArk CCP
- HashiCorp Vault
- Thycotic Secret Server
- Beyond Trust
- AWS Secrets Manager
Any credential store plugin you choose to use must be Linux-compatible.
To disable the default plugins, set the
Plugins.SecureStores.Default key as an empty string in the appsettings.json file. See Configuring appSettings for details.
If you want to add custom secure store assemblies, you can do so via the
uipathctl command line tool, using the uipathctl config orchestrator upload command:
uipathctl config orchestrator upload --securestore-plugins-directory /path/to/plugins/directoryuipathctl config orchestrator upload --securestore-plugins-directory /path/to/plugins/directoryPlugin settings are configured in
appSettings using the convention for configuration keys. See Configuring appSettings for details.
Important: Plugins must not write to any storage apart from
/tmp.
If you use an external storage configuration at the cluster level, you must indicate this by including the
--is-external-storage parameter.
