automation-suite
2.2510
true
- Overview
- Requirements
- Deployment templates
- Manual: Preparing the installation
- Manual: Preparing the installation
- Step 2: Configuring the OCI-compliant registry for offline installations
- Step 3: Configuring the external objectstore
- Step 4: Configuring High Availability Add-on
- Step 5: Configuring SQL databases
- Step 7: Configuring the DNS
- Step 8: Configuring the disks
- Step 9: Configuring kernel and OS level settings
- Step 10: Configuring the node ports
- Step 11: 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
- Kerberos authentication 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 Automation Suite Robots
- Step 15: Configuring the temporary Docker registry for offline installations
- Step 16: Validating the prerequisites for the installation
- Running uipathctl
- Manual: Performing the installation
- Post-installation
- Cluster administration
- Managing products
- Getting Started with the Cluster Administration portal
- Migrating Redis from in-cluster to external High Availability Add-on
- Migrating data between objectstores
- Migrating in-cluster objectstore to external objectstore
- Migrating from in-cluster registry 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
- Scaling a single-node (evaluation) deployment to a multi-node (HA) 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
- Product-specific configuration
- Best practices and maintenance
- Troubleshooting
- How to troubleshoot services during installation
- How to reduce permissions for an NFS backup directory
- 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 work with certificates
- How to schedule Ceph backup and restore data
- How to collect DU usage data with in-cluster objectstore (Ceph)
- How to install RKE2 SELinux on air-gapped environments
- How to clean up old differential backups on an NFS server
- Error in downloading the bundle
- Offline installation fails because of missing binary
- Certificate issue in offline installation
- SQL connection string validation error
- 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
- Temporary registry installation fails on RHEL 8.9
- Frequent restart issue in uipath namespace deployments during offline installations
- DNS settings not honored by CoreDNS
- Upgrade fails due to unhealthy Ceph
- RKE2 not getting started due to space issue
- Upgrade fails due to classic objects in the Orchestrator database
- Ceph cluster found in a degraded state after side-by-side upgrade
- Service upgrade fails for Apps
- In-place upgrade timeouts
- Upgrade fails in offline environments
- snapshot-controller-crds pod in CrashLoopBackOff state after upgrade
- Upgrade fails due to overridden Insights PVC sizes
- Upgrade failure due to uppercase hostname
- 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
- Missing Ceph-rook metrics from monitoring dashboards
- Mismatch in reported errors during diagnostic health checks
- No healthy upstream issue
- Redis startup blocked by antivirus
- Running High Availability with Process Mining
- Process Mining ingestion failed when logged in using Kerberos
- 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
- Exploring summarized telemetry
Automation Suite on Linux installation guide
Last updated Mar 26, 2026
AWS Marketplace deployment parameters
This page documents the AWS parameters you need to configure when deploying Automation Suite to AWS.
Table 1. Network choice
| Parameter label (name) | Default value | Description |
|---|---|---|
| Deploy to an existing VPC | false | Choose true to deploy Automation Suite in an existing VPC. |
Table 2. Network configuration
Note:
Configure this section only when deploying Automation Suite in an existing VPC.
| Parameter label (name) | Default value | Description |
|---|---|---|
| VPC CIDR | 10.0.0.0/16 | VPC CIDR block. Example: x.y.0.0/16, x.y.z.0/24. |
| VPC ID | Requires Input | ID of the existing VPC. |
| Public subnet IDs | Blank string | List of public subnet IDs to deploy the internet-facing Load Balancer and the Bastion host. |
| Private Subnet IDs | Requires Input | List of private subnet IDs. |
Table 3. Availability Zone configuration
Note:
Configure this section only when deploying Automation Suite in a new VPC.
| Parameter label (name) | Default value | Description |
|---|---|---|
| Availability Zones | Requires input | Choose up to three Availability Zones to use for the VPC subnets. |
Table 4. Common networking configuration
| Parameter label (name) | Default value | Description |
|---|---|---|
| Number of Availability Zones | 2 | Choose the number of Availability Zones to use in the VPC. This must match the number of zones selected in the Availability Zones parameter. |
| Deploy Bastion host | true | Deploy a Bastion host inside the public subnet. |
| CIDR for bastion's ingress for SSH traffic | Empty string | Ingress Security Group CIDR (for SSH). Configure this parameter only if you have set the Deploy Bastion host parameter to true. Set to x.x.x.x/32 to allow one specific IP address access, 0.0.0.0/0 to allow all IP addresses access, or another CIDR range. |
Table 5. Automation Suite node configuration
| Parameter label (name) | Default value | Description |
|---|---|---|
| Server instance type | c5.4xlarge | Choose the node type for the Server node instances. |
| Server instance count | 3 | Choose the number of nodes to be deployed as Server node instances. |
| Agent instance type | c5.4xlarge | Choose the node type for the Agent node instances. |
| Agent instance count | 1 | Choose the number of nodes to be deployed as Agent node instances. |
| GPU agent instance type | p3.2xlarge | Choose the node type for the GPU Agent node instance. |
| AS Robots agent instance type | c5a.4xlarge | Choose the node type for the AS Robots Agent node instance. |
| AS Robots agent instance count | 1 | Choose the number of nodes to be deployed as AS Robots Agent node instances. |
Table 6. Automation Suite instance configuration
| Parameter label (name) | Default value | Description |
|---|---|---|
| Instance key pair | Requires input | Existing key pair to connect to virtual machine (VM) instances. |
| IAM role ARN | Blank string | ARN of a pre-deployed IAM Role with sufficient permissions for the deployment. Leave empty to create a new role automatically during deployment. |
| IAM role name | Blank string | Name of a pre-deployed IAM role with sufficient permissions for the deployment. Leave empty to create a new role automatically during deployment. |
Table 7. Automation Suite deployment configuration
| Parameter label (name) | Default value | Description |
|---|---|---|
| Enable cluster backup | true | Enable the cluster backup. |
| Use a shared bucket for external storage | false | Enable a shared bucket across products. If enabled, Process Mining and Data Service still require a dedicated bucket each. |
| Load balancer | ALB | Select either an Application Load Balancer (ALB) or a Network Load Balancer (NLB). If you select a Network Load Balancer, then you need to manually configure the TLS certificates post deployment. |
| Ingress Security Group CIDR (for https) | Empty string | Ingress Security Group CIDR (for HTTPS). Set the CIDR to allow access to Automation Suite. Set the CIDR tox.x.x.x/32 to allow one specific IP address access, 0.0.0.0/0 to allow all IP addresses access, or another CIDR range. |
| Perform installation | true | Perform the Automation Suite installation. Choose false to perform only infrastructure provisioning and configuration. |
| Automation Suite version | e.g. 2023.10.1 | Automation Suite version to install |
| Add GPU-enabled VMs | false | Choose true to add a GPU-enabled VM to the deployment. |
| Extra configuration keys | Blank string | Extra configuration keys to add to the cluster configuration. Leave empty to use the default configuration. |
| Validity of the self-signed certificate | 1825 | Validity (in days) of the self-signed certificate that the deployment uses to encrypt traffic inside the VPC. |
| Disable presigned URL | false | Enable or disable objectstore access via pre-signed URLs. |
Table 8: Automation Suite external registry configuration
| Parameter label (name) | Default value | Description |
|---|---|---|
| External registry Fully Qualified Domain Name | Requires input | FQDN for the external registry. Leave empty to not use an external registry. |
| External registry user name | Requires input | User name for connecting to the external registry. Leave empty to not use an external registry. |
| External registry password | Requires input | Password for connecting to the external registry. Leave empty to not use an external registry. |
Table 9. Automation Suite service configuration
| Parameter label (name) | Default value | Description |
|---|---|---|
| Service install flags (multiple) | true | Choose if a specific service is installed in the cluster. |
Table 10. Automation Suite external Orchestrator configuration
| Parameter label (name) | Default value | Description |
|---|---|---|
| Connect AI Center to an external Orchestrator | false | Register AI Center to an external Orchestrator. |
| Orchestrator URL | Blank string | URL of the external Orchestrator to which AI Center connects. Example: https://my-orchestrator.net |
| Identity URL | Blank string | URL of the Identity server used to authorize AI Center. Example: https://my-orchestrator.net/identity |
| Base64 encoded Orchestrator certificate | Blank string | Base64 encoded Orchestrator certificate string Example: UExBQ0VIT0xERVI= |
| Base64 encoded Identity certificate | Blank string | Base64 encoded Identity certificate string Example: UExBQ0VIT0xERVI= |
Table 11. DNS or SSL configuration
| Parameter label (name) | Default value | Description |
|---|---|---|
| Hosting FQDN | Requires input | Fully qualified domain name (FQDN) for Automation Suite. This must be either a subdomain or root domain of the ID of Amazon Route 53-hosted zone parameter. |
| ID of Amazon Route 53-hosted zone | Blank string | Enter the ID of the Amazon Route 53-hosted zone or leave blank. For details, see. |
| ARN of the ACM-hosted certificate | Blank string | ARN of the certificate present in the Amazon Certificate Manager (ACM) to use with the ALB. Leave empty to create the public certificate during deployment. |
| Use internal load balancer | false | Choose if you want to use an internal load balancer. |
Table 12. Amazon RDS configuration
| Parameter label (name) | Default value | Description |
|---|---|---|
| Engine of SQL Server deployed on Amazon RDS | sqlserver-se | Choose the Amazon Relational Database Service (Amazon RDS) SQL engine |
| Version of SQL Server deployed on Amazon RDS | 15.00 | Choose the Amazon RDS SQL version. |
| AWS KMS Key Id used to encrypt Amazon RDS storage | Blank string | KMS Key ID to use for the encryption of the Amazon RDS storage. Leave empty to skip encrypting the Amazon RDS storage. |
- Table 1. Network choice
- Table 2. Network configuration
- Table 3. Availability Zone configuration
- Table 4. Common networking configuration
- Table 5. Automation Suite node configuration
- Table 6. Automation Suite instance configuration
- Table 7. Automation Suite deployment configuration
- Table 8: Automation Suite external registry configuration
- Table 9. Automation Suite service configuration
- Table 10. Automation Suite external Orchestrator configuration
- Table 11. DNS or SSL configuration
- Table 12. Amazon RDS configuration