Skip to content

Conversation

@Tmonster
Copy link
Contributor

@Tmonster Tmonster commented Jan 19, 2026

DO NOT MERGE, this is a breaking change and we need to discuss if this is a break we want to make.

Follow up for https://github.com/duckdblabs/duckdb-internal/issues/6620

In v1.4.4 duckdb-httpfs will automatically read environment variables like AWS_SECRET_ACCESS_KEY, and AWS_SECRET_KEY_ID and populate the config values s3_secret_access_key and DBConfigOptions with those environment variables. These config values would then be used for any remote reads on a blob storage like s3/r2. #182 introduced the ability to disable the automatic use of these values during remote reads, it did not disable automatically reading and setting those values.

With this PR for v1.5, we will disable auto loading environment values not prefixed with DUCKDB into the config options, and only do when the user requests it. To allow a user to set config values from environment variables, we introduce the function inherit_aws_config_from_environment() that a user can call which will set the config values s3_region, s3_secret_access_key, s3_session_token, s3_endpoint, s3_use_ssl, s3_kms_key_id, and s3_requester_pays. These config options are only set locally, we can set these config options globally if needed.

@carlopi carlopi self-requested a review January 19, 2026 10:12
@Tmonster Tmonster changed the title Add inherit_aws_config_from_environment function so user can set s3 config values using environment variables [DNM] Add inherit_aws_config_from_environment function so user can set s3 config values using environment variables Jan 19, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant