When using a service like AWS's ElasticCache with SSL enabled, there needs to be a few changes made to the redis URL. First, the scheme needs to be changed to rediss. This could be done already. The other change that is needed is to add a parameter to the end of the url like ?ssl_cert_reqs=CERT_REQUIRED. The problem with the existing configuration is that the database, e.g \6 was added to the end of the url string, and the parameters need to be located after the database URL. To accomplish this, I added a new redisParameters section to the kobotoolbox section which defaults to an empty string, and then changed the redis variables to include this in the URL format. I've tested this locally with our Kobo deployment and it's working correctly with Elasticache.
Yes, you are correct. This PR will hopefully address that issue, but without that there is certainly less urgency to merge this until that one is released.
When using a service like AWS's ElasticCache with SSL enabled, there needs to be a few changes made to the redis URL. First, the scheme needs to be changed to
rediss
. This could be done already. The other change that is needed is to add a parameter to the end of the url like?ssl_cert_reqs=CERT_REQUIRED
. The problem with the existing configuration is that the database, e.g\6
was added to the end of the url string, and the parameters need to be located after the database URL. To accomplish this, I added a newredisParameters
section to the kobotoolbox section which defaults to an empty string, and then changed the redis variables to include this in the URL format. I've tested this locally with our Kobo deployment and it's working correctly with Elasticache.