1

We self-host Redash in AWS with Fargate, Elasticache Redis & RDS. Redis was reachable when Encryption in-transit was OFF. After we changed the REDASH_REDIS_URL to encryption enabled endpoint, there is no connection.

Fargate started the service with the latest Redash docker image to spin up. All security groups configured inbound allowing port 6379 & 443. Without “encryption in-transit”, the data is vulnerable. Does anyone have experience to make Redis Encryption in-transit work for Redash? Assistance highly appreciated.

Original URL was http://<fargate_ip>:5000/ reachable when Redis is direct to non encryption in-transit Redis url.

  • Redash Version: V.10.0.0
  • Browser/OS: Chrome 90.0.4430.212
2

Try changing the redis URL in your environment from:

redis://<ip address of your elasticache>:6379/0

to

rediss://<ip address of your elasticache>:6379/0

Background

ElasticCache uses SSL for encrypted-in-transit connections.

Redash uses the official redis python client (see here), which requires an extra s on the connection string to support SSL.

1 Like
3

Thank you @jesse That works!! New revision I changed REDASH_REDIS_URL=rediss://…, no more pending, logs normally.

1 Like