Elasticache ERR_TLS_CERT_ALTNAME_INVALID when using custom DNS name.
We're using AWS Elasticache (Redis) with encryption enabled for Novu.
A custom DNS CNAME is pointing to elasticache cluster.
When connecting to the cluster by the custom dns name Novu throws ERR_TLS_CERT_ALTNAME_INVALID error which is fine due to the origin of the elasticache cluster certificate.
We're trying to ignore the error with REDIS_TLS env variable but it seems to be ignored.
ENV vars we use:
REDIS_HOST=elasticache-novu.staging.example.com
REDIS_TLS={"servername":"elasticache-novu.staging.example.com","rejectUnauthorized":false}
REDIS_PASSWORD=example
REDIS_DB_INDEX=2
REDIS_PORT=6379
We do really wanna use our custom dns name as Redis endpoint and expect rejectUnauthorized in REDIS_TLS to turn off host verification which is apparently not the case.
3 Replies
We did try using 'REDIS_CLUSTER_*' and 'ELASTICACHE_*' env vars but Novu didn't seem to recognise them and tried to connect to localhost all the time.
@dkart
Could you please create a post in #⚓│community-self-host channel?
Thank you for the response. The post was created.