- 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
- Business Rules
- Storage Buckets
- Indexes
- Orchestrator testing
- Resource Catalog Service
- Integrations
- Troubleshooting
Orchestrator user guide
Automation Cloud™ Robots - VM
|
Feature |
Testing - consumed amount 1 |
Production - consumed amount |
Details |
|---|---|---|---|
|
Automation Cloud™ Robots - VM |
By machine size:
By cost profile: Selecting Fast or Always cost profiles adds extra RUs to the existing consumption rate:
|
By machine size:
By cost profile: Selecting Fast or Always cost profiles adds extra RUs to the existing consumption rate:
|
Consumption: Robot units are consumed from the tenant's annual available RUs, shortly after it is created. Additional costs: A licensed machine can run as long as needed with no additional RU consumption. Reserved RUs: The required amount of RUs to be consumed by each Cloud Robot - VM machine is reserved per month, at the turn of each month. |
Once you create an Automation Cloud™ Robots - VM, the required robot units are consumed. To ensure continous operation throughout the months, we keep track of how many robot units your cloud machines need for the next month, and we internally reserve them. At the beginning of each billing month, we automatically deduct the necessary robot units for your existing VMs from the monthly robot unit pool.
For this reason, you could find that the robot unit amount for a tenant can be lower than you would expect at the start of the month.
For example, consider a tenant with an allocation of 30,000 robot units. If this tenant maintains three VM standard machines as of May 31st, each requiring 6,000 robot units, then on June 1st, a total of 18,000 robot units (3 machines x 6,000 robot units/machine) is automatically deducted from your tenant. This results in an available balance of 12,000 robot units for June.
Deletion of an Automation Cloud™ Robots - VM machine during the month does not refund the robot units consumed to create it. However, for the rest of that month, you can create another similar VM machine without using any extra robot units. Once robot units are used, they allow one VM machine to run for the entire month, and are not bound to a specific instance.
To lower the monthly robot unit usage for your current virtual machines, you can delete a VM before the current month ends. This prevents the reservation and subsequent consumption of robot units for that machine from the following month allocation.
