DigitalOcean Spaces

Connect & Ingest data from / into a DigitalOcean Spaces 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. nyc3.digitaloceanspaces.com)

Using sling conns

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

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

Environment Variable

In JSON/YAML format:

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

Sling Env File YAML

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

connections:
  DO_SPACES:
    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 or open a Github Issue here.

Last updated