When deploying grafana with an aws rds postgres as backend db I came across the following error:
Error: ✗ pq: no pg_hba.conf entry for host "<my-custom.grafana.pod.ip>", user "<some-user>", database "<my-custom-db-name>", no encryption
Turns out the rds was deployed with a default parameter group, which had rds.force_ssl set to 1. For my scenario having it turned off was fine. The solution was to re-deploy (a reboot also works) the rds with a customized parameter group based off of the default one with rds.force_ssl set to 0.
Top comments (0)