latest duckdb 1.4.2 breaks when i use AWS_SHARED_CREDENTIALS_FILE

[ruiyang2015]

i set all my aws credentials in the aws credential file specified in AWS_SHARED_CREDENTIALS_FILE, but after duckdb 1.4.2 upgrade, i am getting this error:

_duckdb.Error: Secret Validation Failure: no profile '87f67fded9e2fca7b3a8cb22bffe0fb2e7d408794ccc54d78e57b47b922c0204' found in config file /home/ascend/.aws/config

my env is running in ec2, and the default location contains $HOME/.aws/config does not exists, according to boto3 behavior, if profile does not exists, it should always use the credentials location.

i am using following s3 secret:

    CREATE OR REPLACE SECRET ducklake_s3_{profile} (
      TYPE s3,
      PROVIDER credential_chain,
      CHAIN 'config',
      PROFILE '{profile}',
      REFRESH 'auto',
      SCOPE '{s3_config.s3.root}'
    )

duckdb-aws should support credential file only use case too as this is boto3 default behavior.

[Tommo56700]

I see a similar issue in 1.4.2:

CREATE OR REPLACE SECRET (
    TYPE s3,
    PROVIDER credential_chain,
    PROFILE '{profile}'
)

_duckdb.Error: Secret Validation Failure: no profile '{profile}' found in config file ~/.aws/config

Even though the ~/.aws/config file contains the profile.

This works fine on 1.4.1