You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
I'm facing an issue using AWS SecretsManager JDBC driver with RDS Proxy and Alternating User secret rotation.
It seems that RDS Proxy is not able to handle properly such rotation since it is limited to fetch only the AWSCURRENT secret version stage, and this leads to the following error:
org.postgresql.util.PSQLException: FATAL: This RDS proxy has no credentials for the role <db_user>. Check the credentials for this role and try again.
I've already opened a Feature Request to AWS on this, but in the meantime I'd like to discuss such topic with you.
In my opinion everything should work as expected if the driver could intercept also the above error as an authentication error and refresh the secret cache accordingly.
What do you think?
Could this be feasible?
Any other idea?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi,
I'm facing an issue using AWS SecretsManager JDBC driver with RDS Proxy and Alternating User secret rotation.
It seems that RDS Proxy is not able to handle properly such rotation since it is limited to fetch only the AWSCURRENT secret version stage, and this leads to the following error:
I've already opened a Feature Request to AWS on this, but in the meantime I'd like to discuss such topic with you.
In my opinion everything should work as expected if the driver could intercept also the above error as an authentication error and refresh the secret cache accordingly.
What do you think?
Could this be feasible?
Any other idea?
Thank you.
Beta Was this translation helpful? Give feedback.
All reactions