- 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
Checking the infrastructure prerequisites
Prerequisite checks help you ensure that the required cloud infrastructure is provisioned appropriately and is accessible by the client machine before starting the Automation Suite installation.
For a list of prerequisite checks that the Automation Suite installer performs, see Prerequisite checks.
Generating configurations automatically
The Automation Suite installer can automatically generate the following configurations on your behalf:
- The SQL databases required for the installation on the SQL server based if the
sql.create_dbkey is set in yourinput.jsonfile. - The object storage buckets required in your cloud provider if the
external_object_storage.create_bucketkey is set in the configuration file.
To allow the installer to generate these configurations, run the following command:
uipathctl prereq create input.json --versions versions.json
uipathctl prereq create input.json --versions versions.json
For details on the flags that you can use with the uipathctl prereq create command, see uipathctl prereq create.
The uipathctl prereq create command does not create the required SQL databases for Process Mining. You must manually create them by following the instructions in Bring your own database.
Checking the prerequisites
To check the prerequisites based on the inputs you configured in the input.json, run the following command:
uipathctl prereq run input.json --versions versions.json
uipathctl prereq run input.json --versions versions.json
For details on the flags that you can use with the uipathctl prereq run command, see uipathctl prereq run.
By default, the uipathctl prereq command checks all the prerequisites. Alternatively, the command also allows you to run strictly the checks that are relevant to you, as follows:
- If you want to exclude components from the execution, use the
--excludedflag. For example, if you do not want to check the database connection strings, runuipathctl prereq --excluded SQL. The command runs all the prerequisite checks except for the SQL-related one. - If you want to include only certain components in the execution, use the
--includedflag. For example, if you only want to check the DNS and objectstore, runuipathctl prereq --included DNS,OBJECTSTORAGE.
You can find the names of the components you can include or exclude from the prerequisite checks in the prerequisite check output. In the example, the first word on each outdented line represents the component name. For example: SQL, OBJECTSTORE, DNS, etc.
You may receive a throttling message from AKS, such as Waited for 1.0447523s due to client-side throttling, not priority and fairness. In this case, allow a few minutes for the command to fully complete or try to re-run it.