UiPath Robot on AWS

Partner Solution Deployment Guide

QS

March 2021
Adrian Tudoran, Razvan-Valetin Grigoras, and Binoy Das, UiPath
Shivansh Singh and Tony Bulding, AWS Integration & Automation team

Refer to the GitHub repository to view source files, report bugs, submit feature ideas, and post feedback about this Partner Solution. To comment on the documentation, refer to Feedback.

This Partner Solution was created by UiPath in collaboration with Amazon Web Services (AWS). Partner Solutions are automated reference deployments that help people deploy popular technologies on AWS according to AWS best practices. If you’re unfamiliar with AWS Partner Solutions, refer to the AWS Partner Solution General Information Guide.

Overview

This guide covers the information you need to deploy the UiPath Robot Partner Solution in the AWS Cloud.

This Amazon Web Services (AWS) Partner Solution deploys UiPath Robot in the AWS Cloud.

UiPath Robot is the agent that runs processes designed in UiPath Studio. A UiPath Robot is split into several components, each being dedicated to a particular automation task. This design allows you to run, identify, and track the work of each component. With UIPath Robots, you can capture data from user interfaces, manipulate applications, and communicate with other systems to perform repetitive business processes.

Costs and licenses

This Quick Start only installs UiPath Robot. It does not require a UiPath Orchestrator instance. If you decide to connect it to UiPath Orchestrator, you must configure UiPath Robot manually. This deployment supports UiPath Orchestrator version 20.4.x and later.

The Quick Start uses only AWS-provided Microsoft Windows images and does not require a subscription to the Amazon Machine Image (AMI).

There is no cost to use this Partner Solution, but you will be billed for any AWS services or resources that this Partner Solution deploys. For more information, refer to the AWS Partner Solution General Information Guide.

Architecture

Deploying this Partner Solution with default parameters builds the following UiPath Robot environment in the AWS Cloud.

Architecture
Figure 1. Partner Solution architecture for UiPath Robot on AWS

As shown in Figure 1, this Partner Solution sets up the following:

  • A highly available architecture that spans two or more Availability Zones.

  • A VPC configured with public and private subnets, according to AWS best practices, to provide you with your own virtual network on AWS.*

  • In the public subnets:

    • Managed NAT gateways to allow outbound internet access for resources in the private subnets.*

    • A Windows bastion host to allow inbound Remote Desktop Protocol (RDP) access to Amazon Elastic Compute Cloud (Amazon EC2) instances in private subnets.*

    • A security group controlling inbound and outbound traffic to the bastion host instances.

  • In the private subnets:

    • Amazon EC2 instances to host UiPath Robot.

    • A security group controlling inbound and outbound traffic to the UiRobot instances.

* The template that deploys this Partner Solution into an existing VPC skips the components marked by asterisks and prompts you for your existing VPC configuration.

Deployment options

This Partner Solution provides the following deployment options:

This Partner Solution provides separate templates for these options. It also lets you configure Classless Inter-Domain Routing (CIDR) blocks, instance types, and UiPath Robot settings.

Deployment steps

  1. Sign in to your AWS account, and launch this Partner Solution, as described under Deployment options. The AWS CloudFormation console opens with a prepopulated template.

  2. Choose the correct AWS Region, and then choose Next.

  3. On the Create stack page, keep the default setting for the template URL, and then choose Next.

  4. 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. When you finish reviewing and customizing the parameters, choose Next.

    Unless you’re customizing the Partner Solution templates or are instructed otherwise in this guide’s Predeployment section, don’t change the default settings for the following parameters: QSS3BucketName, QSS3BucketRegion, and QSS3KeyPrefix. Changing the values of these parameters will modify code references that point to the Amazon Simple Storage Service (Amazon S3) bucket name and key prefix. For more information, refer to the AWS Partner Solutions Contributor’s Guide.
  5. 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.

  6. On the Review page, review and confirm the template settings. Under Capabilities, select all of the check boxes to acknowledge that the template creates AWS Identity and Access Management (IAM) resources that might require the ability to automatically expand macros.

  7. Choose Create stack. The stack takes about 25 minutes to deploy.

  8. Monitor the stack’s status, and when the status is CREATE_COMPLETE, the UiPath Robot deployment is ready.

  9. To view the created resources, choose the Outputs tab.

Postdeployment steps

If you provided a UiPath Orchestrator URL during deployment, log in to UiPath Orchestrator. Then, verify that the UiPath Robot is present and connected to the tenant.

test1
Figure 2. Test the deployment

The deployment creates a MODERN directory called AWSDeployed, which contains UiPath Robot.

  • For an unattended UiPath software robot, the STATUS is N/A because the new local administrator account is not yet logged in. However, you can run jobs.

  • For an attended UiPath software robot, the STATUS is DISCONNECTED because the built-in administrator account is not logged in.

Access the UiPath Robot VM from the bastion host to check that it is deployed successfully. Connect to an attended UiPath software robot through the administrator account. To retrieve the password, use your private key. For an unattended robot, retrieve the user account from the Robots page in UiPath Orchestrator. The user format is domain/username or machinename/username. Use the same password you used during deployment.

test2
Figure 3. Test the deployment

Troubleshooting

For troubleshooting common Partner Solution issues, refer to the AWS Partner Solution General Information Guide and Troubleshooting CloudFormation.

Customer responsibility

After you deploy a Partner Solution, confirm that your resources and services are updated and configured—including any required patches—to meet your security and other needs. For more information, refer to the Shared Responsibility Model.

Feedback

To submit feature ideas and report bugs, use the Issues section of the GitHub repository for this Partner Solution. To submit code, refer to the Partner Solution Contributor’s Guide. To submit feedback on this deployment guide, use the following GitHub links:

Notices

This document is provided for informational purposes only. It represents current AWS product offerings and practices as of the date of issue of this document, which are subject to change without notice. Customers are responsible for making their own independent assessment of the information in this document and any use of AWS products or services, each of which is provided "as is" without warranty of any kind, whether expressed or implied. This document does not create any warranties, representations, contractual commitments, conditions, or assurances from AWS, its affiliates, suppliers, or licensors. The responsibilities and liabilities of AWS to its customers are controlled by AWS agreements, and this document is not part of, nor does it modify, any agreement between AWS and its customers.

The software included with this paper is licensed under the Apache License, version 2.0 (the "License"). You may not use this file except in compliance with the License. A copy of the License is located at https://aws.amazon.com/apache2.0/ or in the accompanying "license" file. This code is distributed on an "as is" basis, without warranties or conditions of any kind, either expressed or implied. Refer to the License for specific language governing permissions and limitations.