Caching

UiPath® products on Automation Suite require caching capabilities. You must provision Cloud Redis (Azure/AKS) or Elasticache (AWS/EKS). For a list of prerequisites and compatible versions, see Compatibility matrix.

Multiple services in Automation Suite, such as Orchestrator and Identity, use Redis as a distributed cache, for speeding up critical and high volume operations. These services store data that is accessed frequently in Redis, to avoid either retrieving the data from the database or doing expensive computations multiple times.

The following recommendations are specific to Azure. The general recommendation is to choose an SKU with at least 1GB capacity and a Service Level Agreement (SLA) for production environments.

For Redis cache requirements, the provisioning plan can vary, depending on the type of environment you want to deploy, such as a testing environment or a production environment:

• Basic: it is not recommended for production deployment since it does not offer Service Level Agreement (SLA). However, it could be used for a test environment.
• Standard C1 (1GB): It provides decent capacity and performance suitable for a majority of installations. It also allows future scaling to higher levels, including Standard C2 or Premium.
• Standard C2: A step above Standard C1, it provides larger capacity and better performance as compared to C1.
• Premium: The most recommended option, as it provides availability zones promoting a higher SLA, and VNet integration for enhanced security.

After provisioning the caching prerequisite, you must pass the access information in input.json, as shown in the following example:

"fabric": {
  "redis": {
    "hostname": "xx",
    "password": "xx",
    "port": 6380,
    "tls": true
  }
}