- Overview
- Requirements
- Installation
- Q&A: Deployment Templates
- Release Notes
- AWS Deployment Architecture
- Step 1: Preparing the AWS deployment
- Step 2: Deploying the Quick Start template
- Step 3: Post-deployment steps
- AWS deployment parameters
- 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 NIC 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
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 a 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.
Each deployment takes about 1 hour and 25 minutes to complete.
You have the following options for launching the AWS CloudFormation template:
Check the AWS Region that’s displayed in the upper-right corner of the navigation bar and make sure it’s the correct region you are deploying in. This Region is where the network infrastructure for UiPath Automation Suite is built. The template is launched in the us-east-1 Region by default.
Here are the deployment parameters you will 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.