Since DuckDB 1.5.3 I'm experiencing a warning about region not being set during CREATE SECRET statement.
- I'm exporting
export AWS_PROFILE=my-profile
- My
~/.aws/config contains
[profile my-profile]
region = eu-central-1
- My
~/.duckdbrc contains
CREATE SECRET (
TYPE s3,
PROVIDER credential_chain,
CHAIN 'env;config',
VALIDATION 'none',
URL_STYLE path
);
However, when running duckdb, I still receive a warning:
duckdb
-- Loading resources from /home/my-user/.duckdbrc
WARNING:
Set region explicitly using REGION 'us-east-1' in your CREATE SECRET statement, adding a region to your profile in ~/.aws/config or configure the AWS_REGION or AWS_DEFAULT_REGION environment variables.
┌─────────┐
│ Success │
│ boolean │
├─────────┤
│ true │
└─────────┘
DuckDB v1.5.4 (Variegata)
Enter ".help" for usage hints.
I use multiple AWS profiles (in different default regions) so I don't want to hard-code the profile and/or region in a CREATE SECRET statement in ~/.duckdbrc.
Since DuckDB 1.5.3 I'm experiencing a warning about region not being set during
CREATE SECRETstatement.export AWS_PROFILE=my-profile~/.aws/configcontains~/.duckdbrccontainsHowever, when running
duckdb, I still receive a warning:I use multiple AWS profiles (in different default regions) so I don't want to hard-code the profile and/or region in a
CREATE SECRETstatement in~/.duckdbrc.