Before proceeding with your AWS deployment, make sure you have reviewed and complied with the following requirements:
Alternatively, you can copy only the needed scripts from the Terraform folders by viewing the Raw contents.
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.
The AWS access key.
The secret/password for the associated
The name of the SSH keypair to use.
The AWS instance type used for Robot. By default this is set to
The local disk size in
GB. Set to
100 by default.
The number of Robots to be created.
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.
The desired name of your environment. This is also used as a prefix to tag the name of resources.
Configure if a local admin password is set. Set to
yes by default.
The desired local admin password. Only required when
set_local_adminpass is set to
CIDR block of your Amazon Virtual Private Cloud.
Used to configure if a public IP address is associated to the EC2 Robot instances.
false by default.
CIDR block of your Security Group.
The Availability Zones for each region.
URL of your Orchestrator instance.
The Orchestrator tenant where the Robot(s) are being added.
The type of Robot to be created. The available options are:
Indicates an API user with full permissions to create and edit Machines, Robots, and Environments.
Indicate the password for the API user.
The local account to be created for the Robot. Set to
robolocal by default but can be edited.
Note: Do not use
The password for the local account.
The role for the local account of the Robot. The available options are:
- From the CLI, change to the directory of your Orchestrator plan. For example:
terraform plan. Review the resources to be deployed and type
terraform 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 type
- The deployment begins and should be completed in approximately 10 minutes per EC2 instance, generating the following output:
The public IP of the Bastion Host.
Updated about a month ago