GitHub user SB-MFJ closed the discussion with a comment: Need help setting up
Superset chart in AWS EKS behind ALB
Alright, the actual error ended up being cache server config.
If you, dear viewer, also go down this rabbit hole, double check:
AWS Elasticache needs TLS to be set on, despite using 6379
```
"supersetNode.connections.redis_ssl.enabled" = "true"
```
if you have been upgrading from a legacy Elasticache before they had user auth,
you might also need to set the username to not blank
```
"supersetNode.connections.redis_user" = "default",
```
and to set the RECAPCHA_PUBLIC/PRIVATE_KEY per Flask App Builder as with using
LDAP you also need to set `AUTH_USER_REGISTRATION = True`
```
# these are google's dev only recaptcha v2 keys
secret: |
...
RECAPTCHA_PUBLIC_KEY = "6LeIxAcTAAAAAJcZVRqyHh71UMIEGNQ_MXjiZKhI"
RECAPTCHA_PRIVATE_KEY = "6LeIxAcTAAAAAGG-vFI1TnRWxMZNFuojJ4WifJWe"
```
Part user error, part weird doc structure between FAB and Superset, part needs
more debug errors.
But It is what it is. And 'it' is over 🥳
GitHub link:
https://github.com/apache/superset/discussions/36296#discussioncomment-15202520
----
This is an automatically sent email for [email protected].
To unsubscribe, please send an email to:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
