- 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
A secretstore in Automation Suite is an external source used to store sensitive credentials. It can be either a Kubernetes Secret or an Azure Key Vault.
To use a secretstore for credentials in Automation Suite, refer to Using a secretstore for credentials.
If you are using Azure Key Vault as your external secret management system and plan to use your own External Secrets Operator, refer to Installing the External Secrets Operator in Kubernetes.
external-secrets to the excluded components list, as follows:
"exclude_components": [
...
"external-secrets"
]"exclude_components": [
...
"external-secrets"
]When deploying Automation Suite, the input.json file typically contains several sensitive data fields and credentials in plain text. To improve security, you can store these
credentials in a secret store instead of including them directly in the input.json file.
A secretstore acts as an external system that securely holds sensitive credentials and configuration data. When configured, Automation Suite retrieves credentials from the defined secret store during deployment.
To enable secretstore usage, add the following section to the input.json file:
"secret_store": {
"enabled": true
}"secret_store": {
"enabled": true
}
When this configuration is enabled, Automation Suite reads credentials from the secretstore instead of directly from the input.json file.
Automation Suite supports the following secretstore types:
If any credential stored in the secretstore changes, you must perform the credential update procedure. For details, refer to Updating credentials.
