AWS recently added a new provider: LoginCredentialsProvider, related to the "aws login" feature they launched in November 2025.
The request here is to add LoginCredentialsProvider to duckdb-aws as an additional provider.
Note
The SDK includes LoginCredentialsProvider in DefaultAWSCredentialsProviderChain only when constructed with a CredentialProviderConfiguration . duckdb-aws uses the no-arg constructor, which doesn't add it to the chain.
Workaround
Workaround 1 is to export an accesskey /secret key via (for instance) aws_creds = boto3.Session().get_credentials(). This isn't great, since it exports a long-lived credential that doesn't rotate.
Workaround 2 is to use export-credentials: w/ CHAIN 'process'. This isn't ideal, using a process based retrieval, but it's something.
[profile duckdb]
credential_process = aws configure export-credentials --profile default
...
AWS recently added a new provider: LoginCredentialsProvider, related to the "aws login" feature they launched in November 2025.
The request here is to add LoginCredentialsProvider to duckdb-aws as an additional provider.
Note
The SDK includes LoginCredentialsProvider in DefaultAWSCredentialsProviderChain only when constructed with a CredentialProviderConfiguration . duckdb-aws uses the no-arg constructor, which doesn't add it to the chain.
Workaround
Workaround 1 is to export an accesskey /secret key via (for instance)
aws_creds = boto3.Session().get_credentials(). This isn't great, since it exports a long-lived credential that doesn't rotate.Workaround 2 is to use export-credentials: w/
CHAIN 'process'. This isn't ideal, using a process based retrieval, but it's something.