Can not Connect to AWS Redis Serverless

[dfoley84]

Bug description

Unable to Connect to Serverless Redis, Error -2 connecting to superset-redis-ttwfnz.serverless.usw2.cache.amazonaws.com:6379.

Don't see an option for Cache TLS within Superset Config.

How to reproduce the bug

Create an AWS Redis Elastic Cache Serverless Instance

Screenshots/recordings

[2024-04-29 15:07:00,882: ERROR/MainProcess] consumer: Cannot connect to redis://superset-redis-ttwfnz.serverless.usw2.cache.amazonaws.com:6379/0: Error -2 connecting to superset-redis-ttwfnz.serverless.usw2.cache.amazonaws.com:6379. Name or service not known.. Trying again in 32.00 seconds... (16/100)

Superset version

master / latest-dev

Python version

3.9

Node version

16

Browser

Chrome

Additional context

No response

Checklist

• [X] I have searched Superset docs and Slack and didn't find a solution to my problem.
• [X] I have searched the GitHub issue tracker and didn't find a similar bug report.
• [X] I have checked Superset's logs for errors and if I found a relevant Python stacktrace, I included it here as text in the "additional context" section.

[mistercrunch]

We pretty much just use Flask-Caching (https://flask-caching.readthedocs.io/en/latest/) which has a super simple interface and good docs.

Looks like there's something around rediss:// with 2 s

[mistercrunch]

For the record I looked to see if our docs could be improved here https://superset.apache.org/docs/configuration/cache#caching, and pointers are decent. I think pointers to other docs are better than trying to recopy things in our docs (say Rediss TLS-specific stuff) and risk things going out-of-sync over time

[StephenKing]

AFAIK ElastiCache Serverless enforces TLS, so it seems use rediss is the way to go and I suggest to close this.

[mistercrunch]

Perfect, please contribute a docs PR if you think things can be improved.