> RedisLabs IIRC also only offers encryption as an enterprise feature, which is something that has always left a bad taste in my mouth. Yeah I didn't like this

> RedisLabs IIRC also only offers encryption as an enterprise feature, which is something that has always left a bad taste in my mouth. Yeah I didn't like this either, given how other "sexy" features that inherently mean you're not using a single instance listening on loopback were prioritised over TLS support. AFAIK their solution was essentially to run a TLS proxy in front of redis, and I'm not sure what they did if anything about any replicated traffic. However, as of v6 (released recently) TLS is builtin. As I explained in the discussion thread for the 6.0 announcement, putting a proxy in front of Redis, for clients that support TLS is like 10% of the problem, when you're using more than one instance. You end up creating a rats nest of tunnels and local port numbers, so that redis internal replication traffic, and internal sentinel traffic, and sentinel to redis traffic is all encrypted too.