- 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 High Availability Add-on
- Step 4: Configuring Microsoft SQL Server
- Step 5: Configuring the load balancer
- Step 6: Configuring the DNS
- Step 7: Configuring the disks
- Step 8: Configuring kernel and OS level settings
- Step 9: Configuring the node ports
- Step 10: Applying miscellaneous settings
- Step 12: Validating and installing the required RPM packages
- Step 13: Generating cluster_config.json
- Cluster_config.json Sample
- General configuration
- Profile configuration
- Certificate configuration
- Database configuration
- External Objectstore configuration
- Pre-signed URL configuration
- ArgoCD configuration
- External OCI-compliant registry configuration
- Disaster recovery: Active/Passive and Active/Active configurations
- High Availability Add-on configuration
- Orchestrator-specific configuration
- Insights-specific configuration
- Process Mining-specific configuration
- Document Understanding-specific configuration
- Automation Suite Robots-specific configuration
- AI Center-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
- 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 15: Configuring the temporary Docker registry for offline installations
- Step 16: Validating the prerequisites for the installation
- Manual: Performing the installation
- Post-installation
- Cluster administration
- Managing products
- Getting Started with the Cluster Administration portal
- Migrating objectstore from persistent volume to raw disks
- Migrating from in-cluster to external High Availability Add-on
- Migrating data between objectstores
- Migrating in-cluster objectstore to external objectstore
- Migrating to an external OCI-compliant registry
- Switching to the secondary cluster manually in an Active/Passive setup
- Disaster Recovery: Performing post-installation operations
- Converting an existing installation to multi-site setup
- Guidelines on upgrading an Active/Passive or Active/Active deployment
- Guidelines on backing up and restoring an Active/Passive or Active/Active deployment
- Monitoring and alerting
- Migration and upgrade
- Migrating between Automation Suite clusters
- 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
- Executing the upgrade
- Performing post-upgrade operations
- Applying a patch
- 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 bucket
- 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 TX checksum offloading
- How to manually set the ArgoCD log level to Info
- How to expand AI Center storage
- How to generate the encoded pull_secret_value for external registries
- How to address weak ciphers in TLS 1.2
- How to check the TLS version
- How to schedule Ceph backup and restore data
- 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
- 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
- Support bundle log collection failure
- Single-node upgrade fails at the fabric stage
- 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 or later
- Upgrade fails in offline environments
- SQL validation fails during upgrade
- snapshot-controller-crds pod in CrashLoopBackOff state after upgrade
- 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
- Pods stuck in Init:0/X
- Missing Ceph-rook metrics from monitoring dashboards
- Running High Availability with Process Mining
- Process Mining ingestion failed when logged in using Kerberos
- After Disaster Recovery Dapr is not working properly for Process Mining and Task Mining
- Unable to connect to AutomationSuite_ProcessMining_Warehouse database using a pyodbc format connection string
- Airflow installation fails with sqlalchemy.exc.ArgumentError: Could not parse rfc1738 URL from string ''
- How to add an IP table rule to use SQL Server port 1433
- Automation Suite certificate is not trusted from the server where CData Sync is running
- Running the diagnostics tool
- Using the Automation Suite support bundle
- Exploring Logs
Q&A: Deployment templates
Q: For the multi-node HA-ready production profile, the processor requirement for the Complete product selection is 96 (v-)CPU/cores. Is this requirement inclusive of server and agent nodes, or does it refer to server or agent nodes?
A: Our documentation indicates that the multi-node HA-ready production profile requires at least 3 server nodes with minimum CPU/RAM per node. As long as this condition is met, the remaining CPU/RAM requirements can be spread over either additional server or agent nodes that also meet the minimum CPU/RAM requirements.
Q: Is a GPU required for Task Mining?
A: No, GPU is not required for Task Mining.
Q: What does node fault tolerance in the UiPath® Automation Suite Install Sizing Calculator refer to? Does it cover agent nodes, only server nodes, or both?
A: The UiPath® Automation Suite Install Sizing Calculator bases the recommendation with fault tolerance so that a minimum of 3 server nodes are always available in the worst case scenario. You can increase the number of servers that can go down without causing the deployment to fail.
Q: Can I use a private domain in Amazon Route 53?
A: Yes, private hosted zones are supported.
Q: Do I need to specify the DNS records in the cloud solution (e.g., AWS) as well? Can I use an on-premises DNS solution with an Automation Suite AWS deployment? For example, in the case of a URL the end-user accesses, does the record need to be resolvable in the cloud or on-premises DNS?
A: You can use non-Amazon Route 53 DNS infrastructure. However, the DNS must be resolvable in the VPC where you perform the deployment.
Q: Which CNI plugin is used as part of Kubernetes? For example, when vendor-supplied, the Kubernetes solution supports integration with VPC/VNET. If using AWS Kubernetes, whenever the vendor creates and deploys workload, pods get IP addresses from the VPC itself. That means the workload can be accessed by AWS or Azure services.
A: We use Cilium CNI. The Kubernetes distribution comes with 3 supported CNIs, but not the AWS-specific one.
Q: Do you customize Service IP and POD IP ranges?
10.42.0.0/16.
Q: When deploying Automation Suite to AWS into an existing VPC, is it possible to use TerraForm instead of CloudFormation?
A: No, it is not possible. We use the native Infrastructure as Code tool from the cloud provider (CloudFormation for AWS, ARM for Azure).
Q:In regard to the previous question, if my standard for IaaC is Terraform, does it mean that I need to develop the Terraform code?
A: If you would like to deploy Automation Suite manually (not using the existing AWS or Azure templates), then yes, you would need to develop the Terraform code. Alternatively, you can use the existing CloudFormation template for deployment or as a base to assist in creating the Terraform code.
Q: How can I estimate the number of specialized nodes required by Task Mining?
A: Task Mining requires/supports 1 dedicated node out of the box.
Q: Can I use Graviton-based processes for the deployment?
A: No, the Kubernetes distribution does not support ARM.
Q: Can Automation Suite be hosted on AMD or only on Intel processors?
A: Either is fine as long as you meet the architecture requirements.
Q: Can I deploy Automation Suite templates on Ubuntu and CentOS?
A: No, Ubuntu and CentOS are not supported.
Q: For an AWS deployment, if an EFS is automatically deployed, how much space does it reserve?
A: EFS does not come with pre-provisioned size. It is pay-as-you-use. EFS will hold all backups for all disks across the cluster, which means it will use 6 TiB of data, the sum of all the nodes storage data disk space.
Q: Does Azure deployment deploy an NFS solution, as AWS does? If it does, how much space does it reserve?
A: NFS is a protocol that has multiple possible implementations. AWS Elastic File System is one such implementation. NFS Server is another implementation. Azure has a different implementation called Azure Files. If you want to have a backup, you need one of these infrastructure elements.
Q: Which is the preferred cloud service provider: Azure or AWS?
A: We do not have a preferred cloud service provider. We support both.
Q: If Autoscaling is enabled, does the node require customized images?
A: Autoscaling uses your RedHat image, on top of which the UiPath® software will be installed. We do not have clear data now, but cold start is in the 5-10 minute range.
Q: Can I use the Standard edition of Microsoft SQL Server?
A: We support Microsoft SQL Server 2016, 2017, and 2019 Standard and Enterprise editions. For more on SQL requirements, see our documentation.
Q: Is the the total vCPU requirement of 96 cores required from the beginning or can it be part of Autoscaling, which will add or remove nodes depending on the resource need?
A: 96 cores are required to power up the system. Subsequently, you can employ different scaling strategies. However, you must not go under that number.
Q: Do I select the RHEL image or is it prescribed in the AWS or Azure templates? If I must select it, what RHEL version should I use when deploying via templates?
A: The deployment uses a basic RHEL image (which is determined at runtime) and creates an autoscaling group template that is applied when the VM is provisioned. This means that all the software is installed when a new EC2 instance is created. The templates use RHEL 8.2 as of now.
Q: Is there any need for VMs other than for the Kubernetes cluster?
A: To run Automation Suite, no additional VMs outside the cluster are required. However, if you do not have existing machines to run UiPath® Robot, then these would likely be required, in addition to any developer VMs or desktops for UiPath Studio (IDE).
Q: Will there be any integration with CloudWatch or Azure Monitor for Kubernetes logs?
A: As of now, there is no integration to push logs to CloudWatch.
Q: Can Automation Suite use open-source database solutions, such as MySQL or PostgreSQL?
A: The Microsoft SQL Server requirement is independent of the cloud where the Automation Suite is deployed.
