- Overview
- Requirements
- Pre-installation
- Preparing the installation
- Installing and configuring the service mesh
- Downloading the installation packages
- Configuring the OCI-compliant registry
- Granting installation permissions
- Installing and configuring the GitOps tool
- Deploying Redis through OperatorHub
- Applying miscellaneous configurations
- Running uipathctl
- 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: Deleting the default tenant
- Performing a single tenant migration
- Migrating between Automation Suite clusters
- Cluster administration
- Product-specific configuration
- Troubleshooting

Automation Suite on OpenShift 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.
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_db
key is set in yourinput.json
file. -
The object storage buckets required in your cloud provider if the
external_object_storage.create_bucket
key 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
uipathctl prereq create
command, see uipathctl prereq create.
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.
input.json
, run the following command:
uipathctl prereq run input.json --versions versions.json
uipathctl prereq run input.json --versions versions.json
uipathctl prereq run
command, see uipathctl prereq run.
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
--excluded
flag. 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
--included
flag. 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.