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
Is your feature request related to a problem? Please describe.
According to the doc, a JDBC driver user should
Record access/secret keys in file ~/.aws/credentials before trying to connect or
Set env variables called AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY with corresponding values before opening an application to browse the DB (e.g. Tableau Desktop or DBeaver)
I find both options not-user-friendly for a regular user.
Describe the solution you'd like
Add option to specify keys in the connection string as it is already done for username and password
For example:
UPD: Once both keys are specified in the connection string, the driver shouldn't create an instance of AWSCredentialsProvider. Specified = both keys are not empty and valid (checksum validation if available).
Additional context
It is relevant for JDBC driver and for ODBC if it supports AWS_SIGv4 authentication method
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
According to the doc, a JDBC driver user should
~/.aws/credentials
before trying to connector
AWS_ACCESS_KEY_ID
andAWS_SECRET_ACCESS_KEY
with corresponding values before opening an application to browse the DB (e.g. Tableau Desktop or DBeaver)I find both options not-user-friendly for a regular user.
Describe the solution you'd like
Add option to specify keys in the connection string as it is already done for username and password
For example:
UPD: Once both keys are specified in the connection string, the driver shouldn't create an instance of
AWSCredentialsProvider
. Specified = both keys are not empty and valid (checksum validation if available).Additional context
It is relevant for
JDBC
driver and forODBC
if it supportsAWS_SIGv4
authentication methodThe text was updated successfully, but these errors were encountered: