automation-suite
2.2510
false
- Overview
- Requirements
- Pre-installation
- Preparing the installation
- Downloading the installation packages
- Configuring the OCI-compliant registry
- Granting installation permissions
- Installing and configuring the service mesh
- Installing and configuring the GitOps tool
- Installing the External Secrets Operator in Kubernetes
- Applying miscellaneous configurations
- Running uipathctl
- Installation
- Post-installation
- Migration and upgrade
- Monitoring and alerting
- Cluster administration
- Product-specific configuration
- Troubleshooting
Automation Suite on EKS/AKS installation guide
Last updated Nov 13, 2025
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.
