- 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
- Audit
- Settings
- Cloud robots
- Folders Context
- Automations
- Processes
- Jobs
- Apps
- Triggers
- Logs
- Monitoring
- Queues
- Assets
- Storage Buckets
- Test Suite - Orchestrator
- Resource Catalog Service
- Authentication
- Integrations
- Troubleshooting
Requirements
-
All cloud robot VMs contain a hypervisor agent (
hvagent
orUiPath VM Agent
), which ensures the running of VMs. You can find it in your CSP installation folder. Add this agent to your allow-list, so that your security agents do not remove or block it. -
We advise against imposing restrictions on your cloud provider subscription that might block the deployment of specific resources, as these resources are crucial to the successful creation and functioning of virtual machines.
-
You need a Microsoft Azure subscription for hosting your cloud robots.
You must set up Azure and get the following details from your Azure administrator to connect Orchestrator:
- Client Id - the unique identifier for the client app registration
- Client Secret Key - the password for the app registration
- Subscription Id - the unique key for your organization's Azure subscription
- Directory (tenant) Id - the unique key for the tenant you use within the Azure subscription.
For instructions, see Setup in Azure below.
You need an Amazon Web Services (AWS) subscription with Amazon Elastic Compute Cloud (Amazon EC2) for hosting your cloud robots.
You must set up AWS and get an AWS access key from your AWS administrator, which consists of:
- Access Key ID - the unique identifier for the Orchestrator connection
- Secret Access Key - the password for this connection.
These are long-term credentials and, like a username and password, Orchestrator needs to use the access key ID and secret access key together to authenticate requests it makes to the AWS API.
For instructions, see Setup in AWS below.
You need a Google Cloud Platform (GCP) subscription which includes Compute Engine for hosting your cloud robots.
You must set up a GCP project and get the following details from your GCP administrator to connect Orchestrator:
- Client Id - the unique identifier for your GCP project
- Private Key - the key for the GCP service account used for the integration.
For instructions, see Setup in GCP below.