- 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: Migrating standalone Test Manager
- Step 10: 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
- 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 creation
- Troubleshooting
- 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
- Robot cannot connect to an Automation Suite Orchestrator instance
- Log streaming does not work in proxy setups
- Velero backup fails with FailedValidation error
- Accessing FQDN returns RBAC: access denied error
Automation Suite on EKS/AKS installation guide
Installing Automation Suite
Installation overview
This page walks you through the high-level installation instructions for Automation Suite.
Before you begin, consider the following:
- To deploy and manage Automation Suite, you must have knowledge of Kubernetes and cloud resource management. If you encounter issues installing and configuring Automation Suite, contact UiPath® Professional Services.
- Before choosing your deployment profile, see Deployment scenarios.
- The installation process generates self-signed certificates on your behalf if you grant the installer admin privileges. You should replace them with certificates signed by a trusted Certificate Authority (CA) as soon as installation completes. For instructions, see Managing the certificates.
- Automation Suite supports enabling Federal Information Processing Standard 140-2 (FIPS 140-2). For details, see Security and compliance.
Running the installation
To check which deployment scenarios are available for Automation Suite, refer to Deployment scenarios.
To install Automation Suite, take the following steps:
-
After successfully validating the prerequisites, you install Automation Suite by running the following command:
uipathctl manifest apply input.json --versions versions.jsonuipathctl manifest apply input.json --versions versions.jsonFor an output example, see Output example: Automation Suite installation.
Note:If you encounter issues while running the installation, rerun the command the installation commands with all the arguments and flags. For details on the issues you might encounter, refer to Troubleshooting.
-
Validate that your installation is successful and services are healthy by running the following command:
uipathctl health check --namespace <uipath> --versions versions.jsonuipathctl health check --namespace <uipath> --versions versions.json