If REDIS Elasti-cache is not available...

The Ira product platform achieves service discovery via either multicasting or REDIS publishing. Since AWS doesn't allow multicast, the only other option is REDIS. Since the default configuration is always geared towards service discovery, the platform expects REDIS to be available.

In HA configurations with 2 or more EC2 instances, the REDIS Elasti-cache connection should be available and accessible to all the EC2 instances for the services to operate.

By default, the iraCpa and iraDialer setups are configured to connect to REDIS Elasti-cache via stunnel.

For non-HA or Standalone setup

Some setup may contain only a single EC2 instance without valid REDIS Elasti-cache connection. Even a standalone setup cannot operate without some kind of REDIS database. In that case, one must enable local REDIS service. It can done using the following commands:


sudo systemctl stop redistunnel
sudo systemctl disable redistunnel
sudo systemctl enable redis-server
sudo systemctl start redis-server


The above 4 commands will disable the remote REDIS connection and activate the local REDIS service. Now the services will be able to self-discover and re-connect.