Hello there. Looks like using AWS credentials from the “Default Credential Provider Chain” (“~/.aws/credentials”) has broken in the new release of 4.4.0. It no longer works with the legacy Amazon Authentication node, nor with the NEW Amazon Authentication either.
Hi @lendio,
welcome to the KNIME community. Checked this with a fresh KNIME 4.4.0 installation on Linux and the default credentials provider chain works as expected. Can you change the console log level to debug and post the logs from the console? (You can find the option in the peferences → KNIME → KNIME GUI)
Cheers
Sascha
1 Like
Thank you Sascha for looking into this. So if I drag in an Amazon Authentication node and hit execute it does “appear” to work, but when chaining it to an S3 node or Athena Connector node it isn’t actually working. Also if I open the “Amazon Authentication” node and hit “Test Connection” it will fail every time.
Hi @lendio,
not sure if your credentials file contains things that the S3 client in KNIME does not understand or contains a broken config. Can you double check your credentials file?
Can you change the console log level to debug and post the logs from the console? (You can find the option in the peferences → KNIME → KNIME GUI)
Cheers
Sascha
Hi there, the credentials file is working as intended as I use the AWS CLI all the time without issues. I also already turned on debugging, but don’t receive any errors in the debugging interface just in the UI as shown in the previously shared screen shot.
So, just to confirm, if you set up your AWS credentials using “aws configure” then you drop in a AWS Authentication node and click the “Test connection” button, your connection succeeds?
Hi @lendio,
can you try to execute the connector node instead of clicking the Browse button? Maybe this brings up more details in the debug console or the KNIME log (View → Open KNIME log).
According to the error message, there seems to be something around Line 5 of your credentials/config file that the AWS Java SDK (used in KNIME) does not understand or somehow handler other than the AWS CLI. I suggest the following:
- Try to enter your access and secret key in the authentication node and test if this works
- If it works, but you still like to use your credentials file, create the credentials file from scratch and start with the minimal entries required (no profiles etc).
My local credentials file with access and secret key works fine with the with the node. Did not test if the “Test connection” button works, but execution the nodes and clicking the browse button worked.
Cheers
Sascha
1 Like
Hello, I had this same issue after upgrading to 4.4. It was resolved when I went into File → Install KNIME Extensions and updated all of the extensions after upgrading or installing 4.4. The key is that you update those extensions after updating to 4.4. I am not sure why but my Default Credential Provider Chain immediately started working after the extension update. I saw this break and used this fix in two separate development environments. Hope that helps!
Chance
1 Like
This topic was automatically closed 182 days after the last reply. New replies are no longer allowed.