Prerequisites
Before proceeding with your AWS deployment, make sure you have reviewed and complied with the following requirements:
- Selected the appropriate Amazon EC2 Instance Type corresponding to the Hardware Requirements of your Robot deployment.
- Installed Terraform.
- Deployed Orchestrator.
- Copied the contents of UiPath Infrastructure GitHub repository.
Note:
Alternatively, you can copy only the needed scripts from the Terraform folders by viewing the Raw contents.
Installation
- Complete the
variables.tffile with the necessary parameters:
| Parameter | Description |
|---|---|
aws_region | The 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_key | The AWS access key. |
secret_key | The secret/password for the associated access_key. |
key_name | The name of the SSH keypair to use. |
aws_app_instance_type | The AWS instance type used for Robot. By default this is set to t2.medium. |
disk_size | The local disk size in GB. Set to 100 by default. |
instance_count | The number of Robots to be created. |
application | The 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. |
environment | The desired name of your environment. This is also used as a prefix to tag the name of resources. |
set_local_adminpass | Configure if a local admin password is set. Set to yes by default. |
admin_password | The desired local admin password. Only required when set_local_adminpass is set to yes. |
cidr_block | The CIDR block of your Amazon Virtual Private Cloud. |
associate_public_ip_address | Used to configure if a public IP address is associated to the EC2 Robot instances. Set to false by default. |
security_cidr_block | The CIDR block of your Security Group. |
aws_availability_zones | The Availability Zones for each region. |
orchestrator_url | The URL of your Orchestrator instance. |
tenant | The Orchestrator tenant where the Robot(s) are being added. |
robot_type | The type of Robot to be created. The available options are: Attended Unattended Development NonProduction |
api_user | Indicates an API user with full permissions to create and edit Machines, Robots, and Environments. |
api_user_password | Indicate the password for the API user. |
robot_local_account | The 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_password | The password for the local account. |
robot_local_account_role | The role for the local account of the Robot. The available options are:localadminlocaluser |
- From the CLI, change to the directory of your Orchestrator plan. For example:
cd C:\terraform. - Run
terraform init. - Run
terraform plan. Review the resources to be deployed and typeterraform apply -auto-approveto deploy the resources.
Note: You can run the command without-auto-approveand it will show all resources which will be deployed, but not begin until you typeYesto confirm. - The deployment begins and should be completed in approximately 10 minutes per EC2 instance, generating the following output:
| Name | Description |
|---|---|
bastion_public_host | The public IP of the Bastion Host. |
Updated 2 years ago