Error authenticating DuckDb to S3 using AWS credentials provider about harlequin HOT 3 CLOSED

The AWS Credentials provider is a relatively new feature of DuckDB. I'm almost certain this is caused by the fact that the version of DuckDB available to Harlequin isn't the latest. You can verify this by executing select version() within Harlequin.

You indicated you installed Harlequin using pip in your global or user space, which is not recommended for exactly this reason. You may have another package in that space that is pinning you to an earlier DuckDB version. I recommend installing pipx and then using pipx to install Harlequin so that you can more easily manage Harlequin's dependencies.

from harlequin.

Actually, re-reading your report, I think you may just need to install and load the AWS extension. The latest versions of DuckDB don't require the AWS extensions and offer a new api that doesn't use call load_aws_credentials()

from harlequin.

OK, I did a clean install on a new virtual env (boto3, duckdb and harlequin) and it worked correctly, so it must have been something to do with versions.

But you do still need to use: call load_aws_credentials() or it will not inherit anything from the boto session.

Thanks for you're reply.

from harlequin.