- 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
- Disaster recovery: Active/Passive configurations
- Generating the configuration file using a wizard
- AKS input.json example
- EKS input.json example
- 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: 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
Generating the configuration file using a wizard
You can generate the input.json configuration file either manually or using the Automation Suite Installer Wizard. While the wizard offers a more user-friendly approach, it currently does not accommodate all possible configuration scenarios.
In some specific instances, manual creation of the configuration file might be required. For details, see Configuring input.json.
To generate input.json using the Automation Suite Installer Wizard, take the following steps:
-
Launch the wizard on port 80 on the local host by running the following command:
- On Linux/macOS:
./uipathctl config generate./uipathctl config generate - On Windows:
uipathctl.exe config generateuipathctl.exe config generate
To launch the wizard on a different port and host, run the following command:
- On Linux/macOS:
./uipathctl config generate --port <your port> --host <your IP address>./uipathctl config generate --port <your port> --host <your IP address> - On Windows:
uipathctl.exe config generate --port <your port> --host <your IP address>uipathctl.exe config generate --port <your port> --host <your IP address>
- On Linux/macOS:
-
In a browser of your choice, launch the wizard by accessing the following URL:
http://localhost:80. If you chose a different host and port, make sure to replacelocalhostand80with the IP address and port where you want to launch the wizard. -
Accept the license agreement.
-
Indicate the platform where you want to host Automation Suite. You can choose from the following options:
- Automation Suite on AKS
Note:
The instructions in this guide are applicable if you choose this option.
- Automation Suite on EKS
Note:
The instructions in this guide are applicable if you choose this option.
- Automation Suite on OpenShift
- Automation Suite on Linux
- Automation Suite on AKS
-
Specify your deployment mode. You can choose from the following options:
- Online - Choose this option to install Automation Suite in an online environment. This deployment mode requires internet access during installation and runtime.
- Offline - Choose this option to install Automation in an offline environment. This deployment mode requires an OCI-compliant container registry.
For details, refer to Deployment scenarios.
-
Indicate your deployment type. You can choose from the following options:
- Highly Available - Choose this option if you want to install Automation Suite in multi-node HA-ready mode.
- Lite mode - Choose this option if you want to install Automation Suite in lite mode.
-
Provide additional details on your initial configuration. Depending on your previous selection, you may have to provide details such as the Automation Suite FQDN, admin username and password, storage class, namespace, ArgoCD project, and ArgoCD application namespace.
-
Indicate the Automation Suite products you want to enable.
For details, refer to Automation Suite products.
-
Provide the details on your SQL database configuration, such as the following:
- Whether you want to bring your own database or you want the Automation Suite installer to create it for you
- Whether you want to use Kerberos authentication
- The Redis cache details
For details, refer to SQL database.
-
Specify the storage configuration details, such as storage type or bucket details.
For details, refer to Storage.
-
If you opted for an offline installation, provide the details of your OCI-compliant registry.
For details, see Configuring the OCI-compliant registry.
-
Provide your certificates details.
For details, refer to Certificates.
-
Provide details on your load balancer configuration.
For details, refer to Networking.
-
Specify the products for which you want to perform advanced configuration such as overwrite platform-level configurations with service-level configurations such as connections strings, objectstore setup, etc.
-
Specify whether you want to bring your own components or allow the Automation Suite installer to install them.
If you bring your own components, you must manually update the generated
input.jsonfile. For details, refer to Bring your own components. -
Download the
input.jsonconfiguration file.
Any feature that is not available during the input.json configuration using the Automation Suite Installer Wizard, can be manually included after downloading the configuration file.