AWS Extension not available

[whyhive-simon]

What happens?

I'm attempting to use the S3 integration features, but I receive AccessDenied code when duckdb attempts to automatically load the AWS extension.

Inspecting my local directory, I can see a aws.duckdb_extension.wasm file, but its contents are;

<?xml version="1.0" encoding="UTF-8"?>
<Error><Code>AccessDenied</Code><Message>Access Denied</Message><RequestId>KGSJ1VKFS5CHH04D</RequestId><HostId>3+HrDJZleZKvcm6dU3X+uhtwXbrRJK+NWoiRJL3JOu2xjn89D3vCr4yB1fIPRUb3iKqkBRyHkS1u/s2WrKcxIxwC4vHBuxinxgSBQz0S/Ss=</HostId></Error>

The error I receive in my environment is

Error: Extension Autoloading Error: An error occurred while trying to automatically install the required extension 'aws':
Extension "https://extensions.duckdb.org/v1.1.1/wasm_eh/aws.duckdb_extension.wasm" could not be loaded because its signature is either missing or invalid and unsigned extensions are disabled by configuration (allow_unsigned_extensions)

But for reproduction, a similar error occurs in the web duckdb shell

To Reproduce

Going to the DuckDb shell and typing

CREATE SECRET s3 ( TYPE S3, PROVIDER CREDENTIAL_CHAIN );

returns

Extension Autoloading Error: An error occurred while trying to automatically install the required extension 'aws':
Extension https://extensions.duckdb.org/v1.1.3/wasm_eh/aws.duckdb_extension.wasm is not available

Browser/Environment:

Chrome

Device:

Windows

DuckDB-Wasm Version:

@duckdb/[email protected]

DuckDB-Wasm Deployment:

shell.duckdb.org

Full Name:

Simon Grant

Affiliation:

WhyHive