Redis in AWS Cloud - AWS ElastiCache Settings

News Knowledge Base
1

What is the procedure for Installation and Configuration of Redis and ElastiCache?

Redis in AWS Cloud : Below Steps are to be performed to install and configure Redis in AWS Cloud,
  • Create Redis Server in AWS
  • Configuration in the Orchestrator server

Create Redis in AWS
  1. Go to AWS console https://aws.amazon.com

  1. Click on Services Search for Redis and Click on the ElastiCache as shown in the screenshot

  1. Click Create to launch the new Redis server


  1. Cluster engine should be Redis and click the same, since Orchestrator supports Redis for session syncing. To create a cluster environment, check the cluster mode for High Availability.

  1. Fill all necessary fields that are required as shown in below screen shot. Do not select “Cluster Mode Enabled."
There is a 40-character limit when naming your cluster. Alpha-numeric characters and hyphens only. The Name must start with a letter and cannot end with a hyphen. The name may not contain two consecutive hyphens.

Description: Any description for your cluster, such as “UiPath Redis Cluster”
Engine Version Compatibility: We recommend the latest version of Redis
Certain Redis functionality, such as Encryption requires versions 4.0 or newer.
Port: 6379
The port number can be changed if desired.
Parameter Group: default
Node Type: Redislabs recommends 15GB of memory in Production
Redis Requirements
Number of Replicas: We recommend a minimum of 2 replicas in Production Environments
Feel free to use 0 for a Dev environment or for a Test/POC deployment.

  1. Click on the Advance Redis Settings.
  2. Provide the necessary information click on create as shown the below screenshot.

Multi-AZ with Auto-Failover: For High Availability of the Redis Nodes
This option is only listed if you have 2 or more nodes.
Subnet Group: If you are using AWS for Orchestrator, select your subnet group of the rest of your deployment. Otherwise “Not in VPC” or Creating a new VPC are both viable options.
Preferred Availability Zones: Either select zones manually or allow AWS to automatically spread your deployment through availability zones by selecting “No Preference”
Security Groups: AWS Security Groups can be selected here as per company protocols and standards
Encryption at-rest: This option is currently being tested, enabling it may cause problems with the Orchestrator.
Encryption in-transit: This option enables encryption of data on-the-wire.
·Requires Redis version 3.2.6 or all versions since 4.0.
Seed RDB file S3 location: Data does not currently need to be imported to AWS ElastiCache.
Backups: Automatic backups are not required for an HA Setup of Redis for Orchestrator.
Maintenance: No preference, or select a window based on internal policies.

Note: Redis and Orchestrator server should be in same network on the AWS.

  1. Once Redis server created, the below is available and up to date. Copy the Primary Endpoint as shown in the below screenshot


Configuration in the Orchestrator server

  1. Go to web.config file and edit below setting

  1. Restart IIS and run Orchestrator.