The idea is:
Support setting of self signed certificate in the connection (nodes and platform)
My use case:
Support Elasticache / MemoryDB connnections or internal redis
Support setting of self signed certificate in the connection (nodes and platform)
Support Elasticache / MemoryDB connnections or internal redis
Both but I would say that the queue mode is a priority because it would allow n8n to be deployed in a painless mode. (fools will say a “cloud native” way)
Hey @Renizmy,
Perfect, As a temporary solution you could use a valid certificate for Redis. Using something like Lets Encrypt makes the process fairly painless although if you are using a managed Redis provider I suspect the certificate would be valid or I would at least expect it to be.
I will let the team know anyway so we can look at adding this.