automation-suite
2.2510
true
Automation Suite on OpenShift installation guide
- Overview
- Requirements
- Pre-installation
- Preparing the installation
- Downloading the installation packages
- Configuring the OCI-compliant registry
- Granting installation permissions with cluster roles
- Granting installation permissions without cluster roles
- Installing and configuring the service mesh
- Installing and configuring the GitOps tool
- Installing the External Secrets Operator
- Deploying Redis through OperatorHub
- 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
- 500 errors and rate limiting on S3 requests in ODF
- External Secrets troubleshooting
- Configuring CSI driver tolerations for ODF 4.20
- Temporal as a Service troubleshooting
- AI Center and Document Understanding pods fail to start with TLS certificate verification enabled
- Studio Desktop cannot load Integration Service connectors and activities
- TLS certificate validation errors
- Manual ArgoCD NetworkPolicy mitigation (GHSA-47m3-95c7-g2g8)
- Configuring resource requests and limits for uipathctl-created workloads
Disaster recovery - Active/Passive
Disaster recovery concepts and implementation for Automation Suite multi-site deployments.
This article walks you through the core concepts and architecture of Automation Suite disaster recovery, covering Active/Passive deployments.
Ensuring continuous business automation is at the core of any automation platform. Automation Suite can withstand the complete failure of nodes, entire data centers, or regions. You can deploy Automation Suite as an Active/Passive configuration.
Automation Suite multi-site deployments in Active/Passive mode support the following scenarios:
- Same-region deployment - Two Automation Suite clusters deployed in the same region;
- Cross-region deployment - Two Automation Suite clusters deployed in different regions.
The following table provides details on which Automation Suite products you can deploy in Active/Passive mode.
| Product | Support for Active/Passive |
|---|---|
| Orchestrator | ✅ |
| Action Center | ✅ |
| Agents | ❌ |
| AI Center | ✅ |
| Apps | ✅ |
| Automation Ops | ✅ |
| Automation Suite Robots | ✅ |
| Computer Vision | ✅ |
| Data Service | ✅ |
| Document Understanding | ✅ |
| Test Manager | ✅ |
| Automation Hub | ❌ |
| Insights | ❌ |
| Healing Agent | ❌ |
| Process Mining | ❌ |
| Integration Service | ✅ |
| LLM gateway | ❌ |
| LLM observability | ❌ |
| ECS | ❌ |
| ScreenPlay | ❌ |
| Semantic Proxy | ❌ |
| Studio Web | ❌ |
| Autopilot for Everyone | ❌ |
| Maestro | ❌ |
| Temporal as a Service (TaaS) | ❌ |
| Autopilot for developers | ✅ |
| Solutions | ✅ |
Note:
- You can install products that are not supported in Disaster Recovery with Active/Passive . However, you cannot use these products when the primary cluster is down.
- For AI Center, the training pipeline functionality is available only in the primary cluster.