- Overview
- Requirements
- Installation
- Post-installation
- Cluster administration
- Managing products
- Managing the cluster in ArgoCD
- Setting up the external NFS server
- Automated: Enabling the Backup on the Cluster
- Automated: Disabling the Backup on the Cluster
- Automated, Online: Restoring the Cluster
- Automated, Offline: Restoring the Cluster
- Manual: Enabling the Backup on the Cluster
- Manual: Disabling the Backup on the Cluster
- Manual, Online: Restoring the Cluster
- Manual, Offline: Restoring the Cluster
- Additional configuration
- Migrating objectstore from persistent volume to raw disks
- Monitoring and alerting
- Migration and upgrade
- Migration options
- Step 1: Moving the Identity organization data from standalone to Automation Suite
- Step 2: Restoring the standalone product database
- Step 3: Backing up the platform database in Automation Suite
- Step 4: Merging organizations in Automation Suite
- Step 5: Updating the migrated product connection strings
- Step 6: Migrating standalone Insights
- Step 7: Deleting the default tenant
- B) Single tenant migration
- 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 automatically clean up Longhorn snapshots
- How to disable TX checksum offloading
- How to address weak ciphers in TLS 1.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
- Automation Suite not working after OS upgrade
- Automation Suite Requires Backlog_wait_time to Be Set 1
- Volume unable to mount due to not being ready for workloads
- RKE2 fails during installation and upgrade
- Failure to upload or download data in objectstore
- PVC resize does not heal Ceph
- Failure to Resize Objectstore PVC
- Rook Ceph or Looker pod stuck in Init state
- StatefulSet volume attachment error
- Failure to create persistent volumes
- Storage reclamation patch
- Backup failed due to TooManySnapshots error
- All Longhorn replicas are faulted
- Setting a timeout interval for the management portals
- Update the underlying directory connections
- Cannot Log in 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 With Error: An Invalid Status Code Was Supplied (Client's Credentials Have Been Revoked).
- Alarm Received for Failed Kerberos-tgt-update Job
- SSPI Provider: Server Not Found in Kerberos Database
- Login Failed for User <ADDOMAIN><aduser>. Reason: The Account Is Disabled.
- ArgoCD login failed
- 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
- After the Initial Install, ArgoCD App Went Into Progressing State
- MongoDB pods in CrashLoopBackOff or pending PVC provisioning after deletion
- Unexpected Inconsistency; Run Fsck Manually
- Degraded MongoDB or Business Applications After Cluster Restore
- Missing Self-heal-operator and Sf-k8-utils Repo
- Unhealthy Services After Cluster Restore or Rollback
- RabbitMQ pod stuck in CrashLoopBackOff
- Prometheus in CrashloopBackoff state with out-of-memory (OOM) error
- Missing Ceph-rook metrics from monitoring dashboards
- Pods cannot communicate with FQDN in a proxy environment
- Using the Automation Suite Diagnostics Tool
- Using the Automation Suite support bundle
- Exploring Logs
Estimating Cloud Infrastructure Costs
On this page, we use the cloud templates as a reference point to evaluate the infrastructure costs required to support Automation suite. We also call out a few additional notes to help forecast the total cost of ownership for Automation Suite. The resulting estimates can approximate your future spending on infrastructure with high confidence for cloud deployments. You can also use the estimates as a reference point to compare the costs of physical bare-metal implementations.
Each cloud template deployment automatically provisions a set of components based on the provided inputs. To check out the list of components for each cloud provider, see the following:
To calculate the cost of the infrastructure provisioned by the cloud templates based on your scenario needs, refer to the following guidelines and estimates.
There are multiple factors impacting the cost of the infrastructure deployed by the cloud templates, such as the following:
- Number of server nodes
- Server node instance type
- Number of agent nodes
- Number of GPU nodes
- GPU node instance type
- Products selected
You can accurately estimate the cost of your cloud infrastructure by taking the following steps:
- Determine the resources your scenario requires using the UiPath® Automation Suite Install Sizing Calculator.
-
Use the pricing calculator of your public cloud provider:
Refer to the following examples to help you get started with the pricing calculators.
The following table describes the multi-node HA-ready production infrastructure cost estimate for the Basic and Complete profiles in the context of the previously introduced guidelines.
The estimates do not account for the load balancers, Bastion, key vault, and backup.
|
Preset hardware configuration |
Number of server nodes |
AWS |
Azure |
|---|---|---|---|
|
3 | |||
|
3 |
Automation Suite seems to have a considerable infrastructure footprint. However, when comparing it with the total amount of infrastructure needed to run production use cases of standalone UiPath products, the costs are similar and, in some cases, even lower for Automation Suite.
To give concrete examples of infrastructure cost differences between Automation Suite and standalone products, we leveraged the pricing calculators of cloud providers where possible, along with our hardware requirements. The following table summarizes the results:
|
UiPath products used in production mode |
Standalone product monthly infrastructure costs |
Automation Suite monthly infrastructure costs |
|---|---|---|
|
Orchestrator (single-node production sizing) |
~$1,600 |
N/A (no single-node production version in Automation Suite) |
|
Orchestrator (with HAA addon) |
~$2,200 |
~$3,300 |
|
Orchestrator (with HAA addon) Insights Action Center Test Manager |
~$2,850 |
~$3,300 |
|
Automation Hub |
N/A (no standalone version) |
~$3,300 |
|
Apps |
N/A (no standalone version) |
~$6,200 (estimate in Azure) |
|
Task Mining |
N/A (no standalone version) |
~$6,200 |
|
Document Understanding |
~$6,200 |
~$6,200 |
|
AI Center |
~$6,200 |
~$6,200 |
In addition, the total costs of supporting Automation Suite are lower compared to standalone product deployments when considering the following:
- Automation Suite requires fewer staff members to maintain operation since fewer machines must be managed as compared to standalone products.
- The IT department does not require any new skills to support additional products because the Automation Suite instance management is the same regardless of which products are used. Therefore, Automation Suite required less IT staff to support the range of UiPath products.
- The infrastructure spend does not change significantly when adding new products to the Automation Suite instance and increasing its ROI (i.e., when adding Automation Hub).
- Automation Suite also includes out-of-the-box monitoring, cluster management, as well as unified admin and end-user experiences across all products.
