Automation Suite on EKS/AKS installation guide

Last updated May 16, 2025

Converting an existing installation to multi-site setup

If you exited the Automation Suite setup, you can convert that into multi-site by taking the following steps:

Convert the standalone Automation Suite cluster into the primary cluster. For details, see the following section.
Install secondary Automation Suite cluster. For details, see Disaster Recovery - Installing the secondary cluster.

Converting a standalone cluster into a primary cluster

To convert an existing Automation Suite cluster into a primary cluster of the multi-site deployment, take the following steps:

Update input.json.
Configure the infrastructure on the first server node.
Configure the fabric and services on the first server node.

Updating `input.json`

Add or modify the required input.json parameters on the first server node. For more details, see the following documentation: Advanced installation experience

Note:

It is recommended to keep the FQDN of your existing Automation Suite setup to avoid reconfiguring all your robots.

Configuring the services and reapplying the manifests

To configure the services and reapply the manifests, run the following command:

uipathctl manifest apply input.json --versions version.jsonuipathctl manifest apply input.json --versions version.json

On this page

Converting a standalone cluster into a primary cluster
Updating input.json
Configuring the services and reapplying the manifests

Was this page helpful?

PREVIOUSDisaster Recovery: Performing post-installation operations

NEXTGuidelines on upgrading an Active/Passive deployment

Support and Services

Get The Help You Need

UiPath Academy

Learning RPA - Automation Courses

UiPath Forum

UiPath Community Forum

Trust and Security

Cookies Policy