automation-suite
2.2510
true
- 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
- 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 installation
- AI Trust Layer
- Troubleshooting
- How to work with certificates
- How to uninstall Automation Suite
- How to uninstall Dapr
- How to uninstall Cert Manager
- How to deploy Insights in a FIPS-enabled cluster
- 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
- Velero backup fails with FailedValidation error
- External Secrets troubleshooting
- Temporal as a Service troubleshooting
- AI Center and Document Understanding pods fail to start with TLS certificate verification enabled
- Fluentd does not export logs in IPv6 environments
Automation Suite on EKS/AKS installation guide
Last updated May 15, 2026
Insights does not currently support FIPS. However, you can deploy Insights in a FIPS-enabled cluster by running it on a dedicated non-FIPS node using node selectors and tolerations.
Take the following steps:
-
Add a non-FIPS node to your FIPS-enabled cluster.
-
Apply a taint to the non-FIPS node to prevent other workloads from scheduling on it, and assign it a label that matches the node selector you will configure in the next step.
-
In the
input.jsonfile, configure Insights to run exclusively on the non-FIPS node using node selectors and tolerations:{ "insights": { "enabled": true, "advanced_configuration": { "global": { "nodeSelectorLabels": { "nodename": "insights" }, "tolerations": [ { "key": "insights", "operator": "Equal", "value": "true", "effect": "NoSchedule" } ] } } } }{ "insights": { "enabled": true, "advanced_configuration": { "global": { "nodeSelectorLabels": { "nodename": "insights" }, "tolerations": [ { "key": "insights", "operator": "Equal", "value": "true", "effect": "NoSchedule" } ] } } } }Note:Make sure the
nodeSelectorLabelsandtolerationsmatch the labels and taints you applied to your non-FIPS node. -
Apply the configuration by rerunning the Automation Suite installer.