Connecting Storage Backends

Locations define cloud storage endpoints — buckets and containers — used as sources or destinations in transfer tasks. Each location references a Secret for credentials, and connects to a specific bucket in a specific region.

RClone configuration options (transfers, chunk sizes, etc.) are set at the Task level, not on locations. Locations define where to connect — tasks define how.

Supported Providers

Each provider has its own page covering credentials, location setup, quirks, and rclone import behavior:

AWS S3

Amazon Simple Storage Service

Azure Blob Storage

Azure Blob containers

Backblaze B2

Cloud storage with generous free tier

Cloudflare R2

S3-compatible object storage

DigitalOcean Spaces

DigitalOcean Spaces Object Storage

Fastly Object Storage

Fastly’s S3-compatible object storage

Fil One

S3-compatible object storage on Filecoin

Filebase

Zero-egress S3-compatible object storage

Google Cloud Storage

GCS buckets

Hetzner

Hetzner Object Storage

Impossible Cloud

EU-sovereign S3-compatible object storage

MEGA S4

MEGA’s S3-compatible object storage

Oracle Object Storage

Oracle S3-compatible endpoint

Rabata

Rabata Object Storage

Railway

Railway-provided S3 buckets

Tigris

Globally distributed S3-compatible storage

Wasabi

Hot cloud storage, S3-compatible

S3 Compatible

Any S3-compatible provider

Creating a Location

Create a secret first

Every location needs credentials. If you haven’t already, create a secret for your cloud provider. The secret’s secret_type must match the location’s location_type.

Navigate to Locations

Go to Locations in your team dashboard and click Add Location.

Configure the location

Fill in the required fields:

Field	Description	Required
name	Descriptive unique name (e.g., “Production S3 Bucket”)	Yes
description	Optional notes about this location	No
location_type	Cloud provider — must match the secret’s `secret_type`	Yes
secret_id	Reference to the credentials secret	Yes
bucket_name	Bucket or container name	Yes
region	Provider region (e.g., `us-east-1`, `westus2`)	Varies
endpoint_url	Custom endpoint URL	S3-compatible only

Region and endpoint requirements vary — see the provider comparison below, or jump straight to your provider’s page for the full setup.

Verify the connection

After creation, DataRaven auto-redirects to the detail page and runs a connection verification automatically.

Connection Verification

DataRaven verifies that a location is reachable and properly configured by testing the actual connection. Verification checks:

bucket_exists — confirms the bucket/container is accessible
permissions — tests list, read, write, and delete operations

Verification Status

Status	Meaning
Verified	Successfully tested within the last 24 hours
Stale	Last successful test was more than 24 hours ago
Never tested	Verification has not been run

Verification runs automatically after creation. Re-run it anytime from the location detail page or via the API to confirm connectivity — especially after rotating credentials or changing bucket settings.

For locations using external vault (BYOV) credentials, verification resolves the vault references to test the connection. If resolution fails, you’ll receive specific error codes: VAULT_FIELD_NOT_FOUND, VAULT_ITEM_NOT_FOUND, VAULT_ACCESS_DENIED, etc.

Provider-Specific Configuration

Every provider needs the same three things — a matching secret, a bucket, and enough information to reach the endpoint — but region and endpoint requirements differ. The comparison below shows the shape at a glance; each provider’s page has the full setup, including credentials, worked examples, and quirks.

Provider	Region	Endpoint URL	Notable
AWS S3	Required	Not needed
Azure Blob Storage	Required	Not needed	SAS URL or account key auth
Backblaze B2	Optional	Not needed	Optimized transfer defaults
Cloudflare R2	Not needed	Required — account-specific	Account ID lives in the endpoint
DigitalOcean Spaces	Not needed	Required — embeds region
Fastly Object Storage	Required — Fastly’s own names	Derived from region	Full-access keys only; reserved bucket prefixes
Fil One	Required	Derived from region	Access keys are region-scoped
Filebase	Not needed	Optional — global default	Legacy endpoint also accepted
Google Cloud Storage	Optional	Not needed	Service account JSON auth
Hetzner	Not needed	Required — embeds region
Impossible Cloud	Required	Derived from region
MEGA S4	Required — picks endpoint	Derived from region	Global buckets; strict object-key and bucket-name rules
Oracle Object Storage	Required	Required
Rabata	Required	Required — embeds region
Railway	Varies	Required — Railway-provided
Tigris	Not needed	Required — `https://t3.storage.dev`
Wasabi	Required	Required — embeds region
S3 Compatible	Varies	Required	Catch-all for unlisted providers

Provider Defaults

DataRaven applies sensible default rclone configuration per provider at the task level. Each provider’s page lists its defaults under At a Glance; you can also query them via the API:

{
  "transfers": 32,
  "b2_hard_delete": false,
  "fast_list": true
}

{
  "s3_no_check_bucket": true
}

Provider defaults are starting points. You can override any of these settings in the task’s rclone configuration.

Updating Locations

You can update the following fields on an existing location:

name, description
bucket_name, region, endpoint_url
secret_id (new secret must have the same secret_type as the location’s location_type)

location_type is immutable. You cannot change a location’s provider after creation. Create a new location instead.

Changing bucket_name, region, endpoint_url, or secret_id affects all tasks currently using this location. Verify the connection after making changes.

Deletion

A location cannot be deleted while it is referenced by any tasks. Attempting to delete returns a 409 Conflict error. To delete a location:

Navigate to the location detail page to see linked tasks
Delete or reassign all tasks using this location
Delete the location

Linked Tasks

The location detail page shows all tasks using this location — grouped by whether it’s the source or destination. Click any task to navigate directly to its configuration.

Tier Limits

Plan	Locations
Free	4
Pro	100

Need more? Upgrade your plan from the billing page.

Required Roles

Action	Minimum Role
View locations	VIEWER
Create / Update / Delete	ADMIN
Verify connection	OPERATOR

The OPERATOR role can run verification without full admin access — useful for on-call engineers troubleshooting connectivity issues.

Getting Started

Core Features

Configuration & Integrations

Developer Platform

Security

Connecting Storage Backends

Supported Providers

AWS S3

Azure Blob Storage

Backblaze B2

Cloudflare R2

DigitalOcean Spaces

Fastly Object Storage

Fil One

Filebase

Google Cloud Storage

Hetzner

Impossible Cloud

MEGA S4

Oracle Object Storage

Rabata

Railway

Tigris

Wasabi

S3 Compatible

Creating a Location

Connection Verification

Verification Status

Provider-Specific Configuration

Provider Defaults

Updating Locations

Deletion

Linked Tasks

Tier Limits

Required Roles

​Supported Providers

AWS S3

Azure Blob Storage

Backblaze B2

Cloudflare R2

DigitalOcean Spaces

Fastly Object Storage

Fil One

Filebase

Google Cloud Storage

Hetzner

Impossible Cloud

MEGA S4

Oracle Object Storage

Rabata

Railway

Tigris

Wasabi

S3 Compatible

​Creating a Location

​Connection Verification

​Verification Status

​Provider-Specific Configuration

​Provider Defaults

​Updating Locations

​Deletion

​Linked Tasks

​Tier Limits

​Required Roles

Supported Providers

Creating a Location

Connection Verification

Verification Status

Provider-Specific Configuration

Provider Defaults

Updating Locations

Deletion

Linked Tasks

Tier Limits

Required Roles