Karthikeyan Venkatraman’s Post

View profile for Karthikeyan Venkatraman, graphic

Engineering Manager- Devops at Instamojo

We recently worked for upgrading AWS RDS Postgresql instances from PSQL version 13 to 15 and on completion of this major version upgrade we ran across an issue with the log messge "no pg_hba.conf entry for host "x.x.x.x", user "<<username>>", database <<db_name>>, no encryption. Applications failed to connect to databases. Upon troubleshooting this issue further , We came to know that rds.force_ssl parameter value is set to 1 by default starting AWS RDS Postgresql 15 which forces the connections to be encrypted by default. For internal reasons, we did not want to enable this (the value remained 0 by default in previous versions of psql) and setting this value to 0 helped resolve the issue. If you are planning to perform major upgrades and want to get rid of these issues in future, It is advised to perform a quick comparison between the old and new parameter groups with the compare parameter group option provided under Actions tab in parameter groups to get drifts between current and future version parameters of parameter group. #awsrds #majorversionupgrade #psql15 #dba #awscloud Repost to share with fellow cloud engineers.

Comparing DB parameter groups

Comparing DB parameter groups

docs.aws.amazon.com

To view or add a comment, sign in

Explore topics