- Le plus récent
- Le plus de votes
- La plupart des commentaires
It is recommended to try and incorporate Secrets Manager in Glue connection properties whenever possible this will help from a security of the credentials and will in some cases simplify the setup of the credentials to be used in the Connection setup.
For the issue you are facing, it looks like the connection is not setup correctly. Typically we don't use user it is username and there is typically another username like admin instead of using default database usernames like sa. Confirm that the username is correct. This is if it is a RDS database. If you did setup SA as the username, try setting up a different username and test with that instead.
Based on the error it looks like you port and URL are correct. Connection type is not in there I assume it is JDBC as well.
Contenus pertinents
- demandé il y a 6 mois
- demandé il y a un an
- demandé il y a 2 mois
AWS OFFICIELA mis à jour il y a 2 ans- AWS OFFICIELA mis à jour il y a 2 ans
Hi Elvis, if I put the user/password directly in JDBC URL, it works. But when I put the parameters in SM, this error happens again. So I think Glue job didn't put the parameters in SM to the JDBC URL correctly. And I don't know why it happens.