I am trying to setup a sentinel of master/slave concept where multiple instances have a single sentinel & slave server, while the master is running a local redis server.
Master - redis.confbind 17.xx.xx.xx 127.0.0.1 <-- master's private ipSlaves - redis.confbind 17.xx.xx.xx 127.0.0.1 <-- slave's private ipslaveof <master-private-ip>Sentinel.conf for (master & slaves)bind 0.0.0.0sentinel monitor redis-primary <master-private-ip> 6379 2sentinel down-after-milliseconds redis-primary 2000sentinel failover-timeout redis-primary 5000
Running on AWS EC2 instance
Firewall allowing inbounds connections between instances
Problem is that sentinal at master cannot connect to the redis server via private ip.when master fails a slave gets promoted to master and changes the ip to the current master private ip (Not public ip) and still have no access to redis private ip servers
I think if i can connect redis-cli -h <master-private-ip> -p 6379
everything will work fine, is there a way i can connect to the redis instance using private ip?
Please note that some of the vms are in a different VPC networks.