# Backblaze B2

## 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. `s3.us-west-001.backblazeb2.com`)

### Using `sling conns`

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

{% code overflow="wrap" %}

```bash
$ sling conns set BACKBLAZE type=s3 bucket=sling-bucket access_key_id=ACCESS_KEY_ID secret_access_key="SECRET_ACCESS_KEY" endpoint=<endpoint>
```

{% endcode %}

### Environment Variable

See [here](https://docs.slingdata.io/sling-cli/environment#dot-env-file-.env.sling) to learn more about the `.env.sling` file.

In JSON/YAML format:

{% code overflow="wrap" %}

```bash
export BACKBLAZE='{"type": "s3", "bucket": "sling-bucket", "access_key_id": "ACCESS_KEY_ID", "secret_access_key": "SECRET_ACCESS_KEY", "endpoint": "<endpoint>"}'
```

{% endcode %}

### Sling Env File YAML

See [here](https://docs.slingdata.io/sling-cli/environment#sling-env-file-env.yaml) to learn more about the sling `env.yaml` file.

```yaml
connections:
  BACKBLAZE:
    type: s3
    bucket: <bucket>
    access_key_id: <access_key_id>
    secret_access_key: '<secret_access_key>'
    endpoint: '<endpoint>'
```

If you are facing issues connecting, please reach out to us at <support@slingdata.io>, on [discord](https://discord.gg/q5xtaSNDvp) or open a Github Issue [here](https://github.com/slingdata-io/sling-cli/issues).