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

AWS S3

Amazon Simple Storage Service

Azure Blob Storage

Azure Blob containers

Google Cloud Storage

GCS buckets

Cloudflare R2

S3-compatible object storage

Backblaze B2

Cloud storage with generous free tier

Wasabi

Hot cloud storage, S3-compatible

Railway

Railway-provided S3 buckets

Oracle Object Storage

Oracle S3-compatible endpoint

Tigris

Globally distributed S3-compatible storage

DigitalOcean Spaces

DigitalOcean Spaces Object Storage

Hetzner

Hetzner Object Storage

Rabata

Rabata Object Storage

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

See Provider-Specific Configuration for which fields each provider requires.

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

Field	Value
region	Required — e.g., `us-east-1`, `eu-west-1`
endpoint_url	Not needed

Standard S3 configuration. Region must match where your bucket was created.

Field	Value
region	Required — Azure region (e.g., `eastus`, `westus2`)
endpoint_url	Not needed

Use the Azure region where your storage account is deployed.

Field	Value
region	Not needed
endpoint_url	Required — `https://<account_id>.r2.cloudflarestorage.com`

Replace <account_id> with your Cloudflare account ID, found in the R2 dashboard.

Field	Value
region	Optional
endpoint_url	Not needed

B2 locations automatically receive optimized defaults: transfers: 32, fast_list: true, b2_hard_delete: false. These are applied at the task level.

Field	Value
region	Required — e.g., `us-east-1`, `eu-central-1`
endpoint_url	Required — `https://s3.<region>.wasabisys.com`

Both region and endpoint URL are required. The endpoint URL must include the region.

Field	Value
region	Depends on Railway config
endpoint_url	Required — Railway-provided S3 endpoint

Field	Value
region	Required
endpoint_url	Required — Oracle S3-compatible endpoint

Field	Value
region	Not needed
endpoint_url	Required — `https://fly.storage.tigris.dev`

Tigris is a globally distributed, S3-compatible object storage service. The standard endpoint is https://fly.storage.tigris.dev.

Field	Value
region	Not needed (embedded in endpoint)
endpoint_url	Required — `nyc3.digitaloceanspaces.com`

DigitalOcean Spaces is S3-compatible object storage. The endpoint URL includes the region (e.g., nyc3.digitaloceanspaces.com, sfo3.digitaloceanspaces.com).

Field	Value
region	Not needed (embedded in endpoint)
endpoint_url	Required — `hel1.your-objectstorage.com`

Hetzner Object Storage is S3-compatible. The endpoint URL includes the region (e.g., hel1.your-objectstorage.com, nbg1.your-objectstorage.com, fsn1.your-objectstorage.com).

Field	Value
region	Required — e.g., `us-east-1`
endpoint_url	Required — `s3.<region>.rabata.io`

Rabata Object Storage is S3-compatible. Both region and endpoint URL are required. The endpoint includes the region (e.g., s3.us-east-1.rabata.io).

Field	Value
region	Depends on provider
endpoint_url	Required

Provider Defaults

DataRaven applies sensible default rclone configuration per provider at the task level. Query defaults via the API:

{
  "transfers": 32,
  "b2_hard_delete": false,
  "fast_list": 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

Google Cloud Storage

Cloudflare R2

Backblaze B2

Wasabi

Railway

Oracle Object Storage

Tigris

DigitalOcean Spaces

Hetzner

Rabata

S3 Compatible

Creating a Location

Connection Verification

Verification Status

Provider-Specific Configuration

Provider Defaults

Updating Locations

Deletion

Linked Tasks

Tier Limits

Required Roles

Getting Started

Core Features

Configuration & Integrations

Developer Platform

Security

​Supported Providers

AWS S3

Azure Blob Storage

Google Cloud Storage

Cloudflare R2

Backblaze B2

Wasabi

Railway

Oracle Object Storage

Tigris

DigitalOcean Spaces

Hetzner

Rabata

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