2 Respuestas
- Más nuevo
- Más votos
- Más comentarios
1
I have solved the problem The problem is caused by the fact that the PGSQL engine is 14+ I changed it back to 13.4 and everything is fine.
respondido hace 5 años
1
Starting from Postgres version 14 scram-sha-256 is the default password encryption type. And it looks like it is not being supported by the JDBC driver used by Glue.
This is how I solved it in my case.
- Create a new parameter group if using the default parameter group, and attach to RDS
- Changed
password_encryptiontomd5 - RDS reboot may be required
- Connect to DB using existing credentials, this must be using
scram-sha-256 - Create a new user and grant access to the required db/schema:
CREATE ROLE glue_readaccess;
GRANT CONNECT ON DATABASE MY_DB TO glue_readaccess;
GRANT USAGE ON SCHEMA public TO glue_readaccess;
GRANT SELECT ON ALL TABLES IN SCHEMA public TO glue_readaccess;
CREATE USER aws_glue WITH PASSWORD '323233232klfdjkfdjkfjkdjfjdfjdkjfdjk';
GRANT glue_readaccess TO aws_glue;
- Check that new user has
encryption_typeto md5, older user should havescram-sha-256. At this moment both types of users should be able to connect to DB with their respective credentials. - Note: From now onwards all new users would have
md5password encryption. Even if we reset the password for old users, those also aremd5 - Use this new user
aws_gluein your Glue connection. This should work. It worked in my case.
respondido hace 3 años
This worked for me too. Thanks @bansalakhil
Contenido relevante
preguntada hace un año
preguntada hace un año
preguntada hace 10 meses
preguntada hace un año

Actually, the problem is not solved, the Glue connection is working fine with RDS with postgres13.x but not on 14.x or 15.x. I am still struggling as I can't revert back to 13.x