- Overview
- Requirements
- Recommended: Deployment templates
- Manual: Preparing the installation
- Manual: Preparing the installation
- Step 1: Configuring the OCI-compliant registry for offline installations
- Step 2: Configuring the external objectstore
- Step 3: Configuring Microsoft SQL Server
- Step 4: Configuring the load balancer
- Step 5: Configuring the DNS
- Step 6: Configuring kernel and OS level settings
- Step 7: Configuring the disks
- Step 8: Configuring the node ports
- Step 9: Applying miscellaneous settings
- Step 11: Validating and installing the required RPM packages
- Step 12: Generating cluster_config.json
- Certificate configuration
- Database configuration
- External Objectstore configuration
- Pre-signed URL configuration
- External OCI-compliant registry configuration
- Disaster recovery: Active/Passive configuration
- Orchestrator-specific configuration
- Insights-specific configuration
- Process Mining-specific configuration
- Document Understanding-specific configuration
- Automation Suite Robots-specific configuration
- Monitoring configuration
- Optional: Configuring the proxy server
- Optional: Enabling resilience to zonal failures in a multi-node HA-ready production cluster
- Optional: Passing custom resolv.conf
- Optional: Increasing fault tolerance
- install-uipath.sh parameters
- Enabling Redis High Availability Add-On for the cluster
- Adding a dedicated agent node with GPU support
- Adding a dedicated agent Node for Task Mining
- Connecting Task Mining application
- Adding a Dedicated Agent Node for Automation Suite Robots
- Step 14: Configuring the temporary Docker registry for offline installations
- Step 15: Validating the prerequisites for the installation
- Manual: Performing the installation
- Post-installation
- Cluster administration
- Monitoring and alerting
- Migration and upgrade
- Step 1: Moving the Identity organization data from standalone to Automation Suite
- Step 2: Restoring the standalone Orchestrator database
- Step 3: Backing up the platform database in Automation Suite
- Step 4: Merging organizations in Automation Suite
- Step 5: Updating the Orchestrator connection strings
- Step 6: Migrating standalone Orchestrator
- Step 7: Deleting the default tenant
- B) Single tenant migration
- Migrating from Automation Suite on Linux to Automation Suite on EKS/AKS
- Upgrading Automation Suite
- Downloading the installation packages and getting all the files on the first server node
- Retrieving the latest applied configuration from the cluster
- Updating the cluster configuration
- Configuring the OCI-compliant registry for offline installations
- Migrating to an external OCI-compliant registry
- Executing the upgrade
- Performing post-upgrade operations
- Product-specific configuration
- Best practices and maintenance
- Troubleshooting
- How to troubleshoot services during installation
- How to uninstall the cluster
- How to clean up offline artifacts to improve disk space
- How to clear Redis data
- How to enable Istio logging
- How to manually clean up logs
- How to clean up old logs stored in the sf-logs bundle
- How to disable streaming logs for AI Center
- How to debug failed Automation Suite installations
- How to delete images from the old installer after upgrade
- How to disable NIC checksum offloading
- How to upgrade from Automation Suite 2022.10.10 and 2022.4.11 to 2023.10.2
- Unable to run an offline installation on RHEL 8.4 OS
- Error in downloading the bundle
- Offline installation fails because of missing binary
- Certificate issue in offline installation
- First installation fails during Longhorn setup
- SQL connection string validation error
- Prerequisite check for selinux iscsid module fails
- Azure disk not marked as SSD
- Failure after certificate update
- Antivirus causes installation issues
- Automation Suite not working after OS upgrade
- Automation Suite requires backlog_wait_time to be set to 0
- Volume unable to mount due to not being ready for workloads
- Cluster unhealthy after automated upgrade from 2021.10
- Upgrade fails due to unhealthy Ceph
- RKE2 not getting started due to space issue
- Volume unable to mount and remains in attach/detach loop state
- Upgrade fails due to classic objects in the Orchestrator database
- Ceph cluster found in a degraded state after side-by-side upgrade
- Unhealthy Insights component causes the migration to fail
- Service upgrade fails for Apps
- In-place upgrade timeouts
- Docker registry migration stuck in PVC deletion stage
- AI Center provisioning failure after upgrading to 2023.10
- Setting a timeout interval for the management portals
- Authentication not working after migration
- Kinit: Cannot find KDC for realm <AD Domain> while getting initial credentials
- Kinit: Keytab contains no suitable keys for *** while getting initial credentials
- GSSAPI operation failed due to invalid status code
- Alarm received for failed Kerberos-tgt-update job
- SSPI provider: Server not found in Kerberos database
- Login failed for AD user due to disabled account
- ArgoCD login failed
- Update the underlying directory connections
- Failure to get the sandbox image
- Pods not showing in ArgoCD UI
- Redis probe failure
- RKE2 server fails to start
- Secret not found in UiPath namespace
- ArgoCD goes into progressing state after first installation
- MongoDB pods in CrashLoopBackOff or pending PVC provisioning after deletion
- Unhealthy services after cluster restore or rollback
- Pods stuck in Init:0/X
- Running the diagnostics tool
- Using the Automation Suite Support Bundle Tool
- Exploring Logs
Step 2: Deploying the Quick Start template
This page explains how to choose your deployment option and how to create the stack.
You are responsible for the cost of the AWS services used while running this Quick Start reference deployment. There is no additional cost for using this Quick Start.
For full details, see the pricing pages for each AWS service used by this Quick Start. Prices are subject to change.
Now that you have configured the AWS account, sign in to that account at https://aws.amazon.com with an IAM user role with the necessary permissions.
The following sections walk you through the steps you need to take to launch the Quick Start and create the stack.
This Quick Start provides two deployment options:
- Deploy UiPath Automation Suite into a new VPC. This option builds a new AWS environment which consists of the VPC, subnets, NAT gateways, security groups, bastion hosts, and other infrastructure components. The UiPath Automation Suite is then deployed directly into this new VPC. To set up the networking and routing infrastructure, you only provide the CIDR block for the VPC that you want to create.
- Deploy UiPath Automation Suite into an existing VPC. With this option, resources are provisioned into an existing AWS VPC, and Automation Suite is deployed there.
Note:
If you use AWS GovCloud, you must deploy Automation Suite into an existing VPC. For more requirements, see Preparing an AWS GovCloud deployment.
Each deployment takes about 1 hour and 25 minutes to complete.
You have the following options for launching the AWS CloudFormation template:
us-east-1
Region by default.
Here are the deployment parameters you need for the templates.
- On the Create stack page, keep the default setting for the template URL, and then choose Next.
- On the Specify stack details page, change the stack name if needed. Review the parameters for the template. Provide values for the parameters that require input. For all other parameters, review the default settings and customize them as necessary. For details on each parameter, see AWS deployment parameters. After reviewing and customizing the parameters, choose Next.
- On the Configure stack options page, you can specify tags (key-value pairs) for resources in your stack and set advanced options. When you finish, choose Next.
- On the Review page, review and confirm the template settings. Under Capabilities, select the two check boxes to acknowledge that the template creates IAM resources and might require the ability to automatically expand macros.
- Choose Create stack to deploy the stack.
- Monitor the status of the stack. When the status is CREATE_COMPLETE, the UiPath Automation Suite deployment is ready.
- To view the created resources, see the values displayed in the Outputs tab for the stack.
You might encounter the following error while providing 3 Availability Zones for the deployment:
HA profile needs 3 RAW devices for ceph OSDs(current: 2) spread across failureDomain: 'zone'
[ManagementTools] [Failed] Installing and configuring Application Lifecycle Management Tools
HA profile needs 3 RAW devices for ceph OSDs(current: 2) spread across failureDomain: 'zone'
[ManagementTools] [Failed] Installing and configuring Application Lifecycle Management Tools
The issue can occur due to insufficient capacity in an Availability Zone for the instance type. Check the Auto Scaling Group activity for messages similar to the following: