- Overview
- Requirements
- Installation
- Post-installation
- Cluster administration
- Monitoring and alerting
- Migration and upgrade
- 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 disable TLS 1.0 and 1.1
- 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 debug failed Automation Suite installations
- How to disable TX checksum offloading
- 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
- Failure After Certificate Update
- Automation Suite Requires Backlog_wait_time to Be Set 1
- Cannot Log in After Migration
- Setting a timeout interval for the management portals
- Update the underlying directory connections
- 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).
- Login Failed for User <ADDOMAIN><aduser>. Reason: The Account Is Disabled.
- Alarm Received for Failed Kerberos-tgt-update Job
- SSPI Provider: Server Not Found in Kerberos Database
- 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
- Unexpected Inconsistency; Run Fsck Manually
- Missing Self-heal-operator and Sf-k8-utils Repo
- Degraded MongoDB or Business Applications After Cluster Restore
- Unhealthy Services After Cluster Restore or Rollback
- Using the Automation Suite Diagnostics Tool
- Using the Automation Suite Support Bundle Tool
- Exploring Logs
AWS deployment parameters
This page documents the AWS parameters you need to configure when deploying Automation Suite to AWS.
The Template-hosting S3 Region parameter must match exactly the AWS region in which you try to deploy. If the region does not match, the deployment does not succeed.
Keep the default settings for the parameters labeled Quick Start S3 bucket name, Quick Start S3 bucket Region, and Quick Start S3 key prefix. If these input parameters are altered, the deployment does not succeed.
|
Parameter label (name) |
Template |
Default value |
Description |
|---|---|---|---|
|
Availability Zones |
|
|
Choose up to three Availability Zones to use for the VPC subnets. |
|
Number of Availability Zones |
|
|
Choose the number of Availability Zones to use in the VPC. For a new VPC, this must match the number you set using the Availability Zones parameter. For an existing VPC, you can set two or three Availability Zones. |
|
Deploy Bastion host |
|
|
Deploy a Bastion host inside the public subnet. |
|
Parameter label (name) |
Template |
Default value |
Description |
|---|---|---|---|
|
VPC CIDR |
|
|
VPC CIDR block, in the format x.x.0.0/16. |
|
VPC ID |
|
|
ID of the existing VPC. |
|
Public Subnets IDs |
|
|
List of public subnet IDs where the internet-facing Load Balancer and the Bastion host will be deployed |
|
Private Subnets IDs |
|
|
List of private subnet IDs. |
|
Parameter label (name) |
Template |
Default value |
Description |
|---|---|---|---|
|
Instance key pair |
|
|
Existing key pair to connect to virtual machine (VM) instances. |
|
Instance AMI id |
|
|
AMI ID to use for the creation of the EC2 instances of the cluster. When the AMI ID is not specified, the default version deployed is RHEL 8.3 for non GPU VM and RHEL 8.2 for GPU VM. |
|
GPU instance AMI id |
|
|
AMI ID to use for the creation of the GPU-enabled EC2 instance. |
|
IAM Role ARN |
|
|
ARN of a pre-deployed IAM Role with sufficient permissions for the deployment. |
|
IAM Role name |
|
|
Name of a pre-deployed IAM Role with sufficient permissions for the deployment |
|
Parameter label (name) |
Template |
Default value |
Description |
|---|---|---|---|
|
Deployment Type |
|
|
Install Automation Suite in single-node evaluation mode or multi-node HA-ready production mode. |
|
Enable cluster backup |
|
|
Enable the cluster backup. |
|
Load Balancer |
|
|
Select either an Application Load Balancer (ALB) or a Network Load Balancer (NLB). If you select a Network Load Balancer, then you must configure the TLS certificates manually post deployment. |
|
Perform Installation |
|
|
Perform the Automation Suite installation. |
|
Automation Suite Version |
|
e.g.
21.10.0 |
Automation Suite version to install. |
|
Automation Suite Product Selection |
|
|
Choose Default platform to install Orchestrator, Action Center, Test Manager, Insights, Automation Hub, Automation Ops. Choose Entire platform to additionally install Apps, AI Center, Task Mining, Document Understanding. |
|
Installer download URL |
|
|
Custom URL for installer download. Leave empty to use the UiPath version. |
| Add GPU enabled VMs |
| false | Choose true to add a GPU-enabled VM to the deployment.
|
|
Extra configuration keys |
|
|
Extra configuration keys to add to the cluster configuration. |
| Validity of the self signed certificate |
|
| Validity, in days, of the self-signed certificate that the deployment uses to encrypt traffic inside the VPC. |
|
Parameter label (name) |
Template |
Default value |
Description |
|---|---|---|---|
|
Service install flags (multiple) |
|
|
Choose if a specific service is installed in the cluster. |
|
Parameter label (name) |
Templates |
Default value |
Description |
|---|---|---|---|
|
Hosting FQDN |
|
|
Fully qualified domain name (FQDN) for Automation Suite. This must be either a subdomain or root domain of the of
ID of Route 53 hosted zone parameter.
|
|
ID of Route 53 hosted zone |
|
|
ID of the Route 53-hosted zone. |
|
ARN of the ACM hosted certificate to use |
|
|
ARN of the certificate present in the ACM (Amazon Certificate Manager) to use with the ALB. |
|
Use Internal Load Balancer |
|
|
Choose if you want to use an internal load balancer. |
|
Parameter label (name) |
Template |
Default value |
Description |
|---|---|---|---|
|
Engine of SQL Server deployed on RDS |
|
|
Choose the RDS Microsoft SQL engine. |
|
Version of SQL Server deployed on RDS |
|
|
Choose the RDS Microsoft SQL version. |
|
KMS Key Id used to encrypt RDS storage |
|
|
KMS Key ID to use for the encryption of the RDS storage. |
| Parameter label (name) | Template | Default value | Description |
|---|---|---|---|
| Template folder |
|
| You must not change the value. |
|
Template-hosting S3 Region |
|
|
Must match the region where you deploy the resources in AWS. For example, if you want to deploy in
us-east-1, select us-east-1.
|
- Table 1. Availability Zone Configuration
- Table 2. Network Configuration
- Table 3. Automation Suite Instance Configuration
- Table 4. Automation Suite Deployment Configuration
- Table 5. Automation Suite Services
- Table 6. DNS or SSL Configuration
- Table 7. RDS Configuration
- Table 8. Quick Start S3 bucket configuration
