- Getting started
- Best practices
- Tenant
- About the Tenant Context
- Searching for Resources in a Tenant
- Managing Robots
- Connecting Robots to Orchestrator
- Storing Robot Credentials in CyberArk
- Storing Unattended Robot Passwords in Azure Key Vault (read only)
- Storing Unattended Robot Credentials in HashiCorp Vault (read only)
- Storing Unattended Robot Credentials in AWS Secrets Manager (read only)
- Deleting Disconnected and Unresponsive Unattended Sessions
- Robot Authentication
- Robot Authentication With Client Credentials
- Configuring automation capabilities
- Solutions
- Audit
- Settings
- Cloud robots
- Folders Context
- Automations
- Processes
- Jobs
- Apps
- Triggers
- Logs
- Monitoring
- Queues
- Assets
- Storage Buckets
- Test Suite - Orchestrator
- Resource Catalog Service
- Integrations
- Troubleshooting
Orchestrator User Guide
Setup in Orchestrator
Now that your cloud service provider is set up, you can proceed to connect Orchestrator to it and set up the elastic robots.
In Orchestrator:
Your provider validates the information and then connects your Orchestrator.
To connect elastic robots to Orchestrator in the cloud, you need to provision a machine template of the type Elastic robot pool. This machine template is used when UiPath manages the robots and they run in your cloud.
When creating the elastic robot pool, you have two options:
- You can allow us to automatically create machines when they're needed based on your generalized cloud VM. This automates the provisioning process for both machines and robots. Whenever a process needs to run, the required number of machines are created. In addition, when the elastic robot pool is first used, we install the required UiPath software to run the robot on the new machines.
- (AWS or Azure only) You can add specific VMs that you want us to use for elastic robot orchestration. This is a limited version of elastic robot orchestration where we can start and stop the VM as needed to run processes and install the required UiPath software to run the robot, but we only use the specified machines. We cannot create new machines for you, nor can we remove machines that you created.
Editing an existing Elastic Robot Orchestration pool triggers a Stop command, which forces a shutdown of all associated VMs. This behavior is by design to ensure the pool picks up any new configurations after the edit.
To create the elastic robot pool:
Your elastic robot pool is now set up and ready to be used in a modern folder to run jobs.
Do not interfere with the cloud resources (VMs, images) once you add them to an elastic robot pool.
For example:
-
do not power cycle the VM manually,
-
do not delete the VM from the CSP while it is still in the pool, or
-
do not connect or disconnect the Robot to/from Orchestrator.
You need to add the elastic robot pool to a folder and grant automation permissions for the folder to the account that uses the virtual machine.
Your folder is now set up and the account is configured.
Now that setup in Orchestrator is also complete, you can start running automations in the cloud.
Test the elastic robot orchestration setup by running your first automation in the cloud.
Creating the first virtual machine can take some time - from 10 minutes to several hours (observed only in Azure). A virtual machine must be available to run a job before you can test-run an automation.
The machines of the Elastic Robot Pool show up in the Machine dropdown when you create an automation. The runtime is the one set at Elastic Robot Pool creation.
In Orchestrator:
- Make sure you have published a project or uploaded a package to Orchestrator.
- Go to Automations > Processes from your folder.
- Create a new process.
- Start the job.