- 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
Step 1: Restoring the standalone product database
Here we introduce a way to use SQL Server Management Studio (SSMS) to restore the database of a standaloneproduct to the Automation Suite SQL Server instance. For details on downloading and installing SQL Server Management Studio, see Migration prerequisites.
-
In SQL Server Management Studio connect to the standalone product database, select Tasks, then choose Deploy Database to Azure SQL.

-
Select Connect to connect to the Automation Suite SQL database. Provide the new database name. Choose the directory to store the temporary database file.

-
Wait for the deployment to complete.

-
Record the connection string for the restored standalone product database in Automation Suite.
Restoring the standalone Orchestrator database on EKS
If you migrate to Automation Suite on EKS, you cannot directly restore the Orchestrator database to the Azure SQL database. You must first back up the standalone Orchestrator database to a file and then restore to the RDS database.
If Orchestrator and Identity share their their database, you can skip step 4. If they have separate databases, you must back them up separately.
- Log into the standalone machine and log into SQL Server using SSMS.
- Back up the standalone Orchestrator database:
-
Go to Databases, right-click the Orchestrator database, select Tasks, and select Back Up.

-
Confirm the backup path.

-
Complete the backup.

-
- Restore the standalone Orchestrator database to RDS on the Automation Suite on EKS instance on the standalone machine
-
Upload the backed up
bakfile to S3 bucket.aws s3 cp <local-file-path> s3://haonan-msi-asair-migration-bucket/<filename>aws s3 cp <local-file-path> s3://haonan-msi-asair-migration-bucket/<filename>Sample:
aws s3 cp "C:\Program Files\Microsoft SQL Server\MSSQL15.SQLEXPRESS\MSSQL\Backup\20230401_0614.bak" s3://haonan-msi-asair-migration-bucket/20230401_0614.bak --region us-west-2aws s3 cp "C:\Program Files\Microsoft SQL Server\MSSQL15.SQLEXPRESS\MSSQL\Backup\20230401_0614.bak" s3://haonan-msi-asair-migration-bucket/20230401_0614.bak --region us-west-2 -
Grant permission to the restored database on AWS.
-
Granting permissions to the restored database on AWS
-
Go to IAM, and create a new role with
AWSBackupServiceRolePolicyForRestorespermissions.
-
Go to RDS and select
Option groups:-
Create a group and provide the following details:
- Name: SqlServerBackupRestore
- Description: xxx
- Engine: Select your DB engine
- Major Engine Version: Select version of your DB instance.
-
Select Create.

-
Select the name of created group to edit it as follows:
-
Select Add.
-
Select SQLSERVER_BACKUP_RESTORE.
-
Select the IAM role you created in the previous steps.
-
Select Immediately to schedule instant change.

-
-
Back to RDSDatabases and select your instance.
- Select Modify.
- Select Option group you created in the previous step.
- Select Next.
- Select Apply immediately (it should not cause service downtime).
- Apply changes by selecting Modify DB instance.
- If you have connection to database from SQL Management Studio, close it and connect again.
-
-
Follow AWS documentation to database backed up bak file to AWS S3 bucket. Sample command:
exec msdb.dbo.rds_restore_database @restore_db_name='UiPath_20230531', @s3_arn_to_restore_from='arn:aws:s3:::haonan-msi-asair-migration-bucket/20230401_0614.bak', @with_norecovery=0,exec msdb.dbo.rds_restore_database @restore_db_name='UiPath_20230531', @s3_arn_to_restore_from='arn:aws:s3:::haonan-msi-asair-migration-bucket/20230401_0614.bak', @with_norecovery=0,