Min.IO

Connect & Ingest data from / into a Min.Io Bucket

Setup

The following credentials keys are accepted:

• bucket (required) -> The name of the Bucket

• access_key_id (required) -> The Access Key ID to access the bucket

• secret_access_key (required) -> The Secret Key to access the bucket

• endpoint (required) -> endpoint hostname for (e.g. http://my.host:9000)

• url_style (required) -> set this to path for reading files using duckdb compute.

• ssh_tunnel (optional) -> The URL of the SSH server you would like to use as a tunnel (example ssh://user:[email protected]:22)

• ssh_private_key (optional) -> The private key to use to access a SSH server (raw string or path to file).

• ssh_passphrase (optional) -> The passphrase to use to access a SSH server.

Using sling conns

Here are examples of setting a connection named MINIO_BUCKET. We must provide the type=s3 property:

$ sling conns set MINIO_BUCKET type=s3 bucket=sling-bucket access_key_id=ACCESS_KEY_ID secret_access_key="SECRET_ACCESS_KEY" endpoint=<endpoint> url_style=path

Environment Variable

In JSON/YAML format:

export MINIO_BUCKET='{type: s3, bucket: sling-bucket, access_key_id: ACCESS_KEY_ID, secret_access_key: "SECRET_ACCESS_KEY", endpoint: <endpoint>, url_style: path}'

Sling Env File YAML

See here to learn more about the sling env.yaml file.

connections:
  MINIO_BUCKET:
    type: s3
    bucket: <bucket>
    access_key_id: <access_key_id>
    secret_access_key: '<secret_access_key>'
    endpoint: '<endpoint>'
    url_style: path

If you are facing issues connecting, please reach out to us at [email protected], on discord or open a Github Issue here.