Subscribe

UiPath Robot

The UiPath Robot Guide

AWS Deployment

Prerequisites

Before proceeding with your AWS deployment, make sure you have reviewed and complied with the following requirements:

📘

Note:

Alternatively, you can copy only the needed scripts from the Terraform folders by viewing the Raw contents.

Installation

  1. Complete the variables.tf file with the necessary parameters:
ParameterDescription
aws_regionThe region where Robot is being deployed. By default this is set to eu-west-2 but can be edited.
See here for the supported Availability Zones.
access_keyThe AWS access key.
secret_keyThe secret/password for the associated access_key.
key_nameThe name of the SSH keypair to use.
aws_app_instance_typeThe AWS instance type used for Robot. By default this is set to t2.medium.
disk_sizeThe local disk size in GB. Set to 100 by default.
instance_countThe number of Robots to be created.
applicationThe Robot and application stack name, used as a prefix to tag the name of resources. By default, this is set to uirobot but can be edited.
environmentThe desired name of your environment. This is also used as a prefix to tag the name of resources.
set_local_adminpassConfigure if a local admin password is set. Set to yes by default.
admin_passwordThe desired local admin password. Only required when set_local_adminpass is set to yes.
cidr_blockThe CIDR block of your Amazon Virtual Private Cloud.
associate_public_ip_addressUsed to configure if a public IP address is associated to the EC2 Robot instances.
Set to false by default.
security_cidr_blockThe CIDR block of your Security Group.
aws_availability_zonesThe Availability Zones for each region.
orchestrator_urlThe URL of your Orchestrator instance.
tenantThe Orchestrator tenant where the Robot(s) are being added.
robot_typeThe type of Robot to be created. The available options are:
Attended
Unattended
Development
NonProduction
api_userIndicates an API user with full permissions to create and edit Machines, Robots, and Environments.
api_user_passwordIndicate the password for the API user.
robot_local_accountThe local account to be created for the Robot. Set to robolocal by default but can be edited.
Note: Do not use administrator.
robot_local_account_passwordThe password for the local account.
robot_local_account_roleThe role for the local account of the Robot. The available options are:
localadmin
localuser
  1. From the CLI, change to the directory of your Orchestrator plan. For example: cd C:\terraform.
  2. Run terraform init.
  3. Run terraform plan. Review the resources to be deployed and type terraform apply -auto-approve to deploy the resources.
    Note: You can run the command without -auto-approve and it will show all resources which will be deployed, but not begin until you type Yes to confirm.
  4. The deployment begins and should be completed in approximately 10 minutes per EC2 instance, generating the following output:
NameDescription
bastion_public_hostThe public IP of the Bastion Host.

Updated 2 years ago


AWS Deployment


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.