The Discourse community is working on enabling in-transit encryption (TLS) for connections to an Amazon Elasticache Redis cluster. Initially, Yevhenii Baraniuk encountered issues as Discourse didn’t support TLS, despite the redis-rb client doing so. Yevhenii Baraniuk began implementing the feature but hit a roadblock due to the hiredis driver not supporting SSL at the time. However, Falco has now created a PR that adds TLS capabilities to Redis connections, which is currently being tested and appears to be working.
Our Discourse uses Redis cluster created in Amazon Elasticache which allows enabling in-transit encryption (TLS). However, once we enable TLS on Elasticache Discourse fails to connect to the Redis.
Looks like Discourse doesn’t support this, although redis-rb client does as mentioned in the similar issue here Redis::ConnectionError: Connection lost (ECONNRESET) when using ElastiCache with TLS enabled · Issue #771 · redis/redis-rb · GitHub
I’m adding pr-welcome on that. Feel free to submit one @Yevhenii_Baraniuk 
Update: I started implementing this feature but faced the problem that hiredis driver which Discourse uses doesn’t support SSL at the moment (as for Jul 2019), though redis-rb client does. I’ll come back to the PR once the new version of hiredis is released which is going to support SSL 
Since hiredis is long dead thanks to @sam I created this PR which adds TLS capabilities to our Redis connections:
https://github.com/discourse/discourse/pull/9119
I’m testing it right now and it works.