Your own storage bucket

By default Datius stores your telemetry for you. On plans that include it (the pricing page shows which), an organization can keep its telemetry in its own bucket instead: Amazon S3, Google Cloud Storage, or any S3-compatible service. Events are stored there as Parquet files, which you own and can query with your own tools as well as through Datius.

Set it up

Create a bucket, and credentials that can read, write, list and delete objects in it (the permissions are below). For Google Cloud, create an HMAC key for a service account.
As an organization admin, open Settings → Organization · Storage & Credentials, and choose Amazon S3 or Google Cloud.
Enter the bucket name, region, access key ID and secret. Leave the endpoint empty for AWS and Google Cloud. For another S3-compatible service (MinIO, Cloudflare R2, Backblaze B2 and the like), enter its endpoint URL.
Click Test connection. Datius writes a small test file, reads it back and deletes it, and says which step failed if one does.
Save. Saving runs the same test, and a bucket that fails it isn't saved. New events are written to your bucket from then on.

The secret is encrypted when it's saved and is never shown again; leave it blank when changing other fields to keep the current one.

Permissions

Datius needs these on the bucket. An AWS IAM policy for a bucket named my-datius-bucket:

JSON

{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Effect": "Allow",
      "Action": ["s3:ListBucket"],
      "Resource": "arn:aws:s3:::my-datius-bucket"
    },
    {
      "Effect": "Allow",
      "Action": ["s3:GetObject", "s3:PutObject", "s3:DeleteObject"],
      "Resource": "arn:aws:s3:::my-datius-bucket/orgs/*"
    }
  ]
}

Delete is needed because Datius periodically merges small files into larger ones, and removes data older than your retention period.

What's in the bucket

Everything goes under one prefix per organization, partitioned by workspace, signal and day:

Text

orgs/<organization-id>/workspaces/<workspace-id>/signals/<signal-key>/year=2026/month=10/day=14/<file>.parquet

Each row is one event, with its timestamp, value and tags. DuckDB, Spark, Athena, BigQuery and most BI tools read these files directly. Datius only touches objects under its own prefix, so the bucket can hold other things too.

Network access

The endpoint must be reachable from the public internet. For your safety, Datius refuses endpoints on private or internal addresses (such as localhost, 10.x.x.x or 192.168.x.x).

If your bucket stops working

If writes to your bucket keep failing because of the bucket itself (the credentials were rotated or revoked, a permission was removed, or the bucket was deleted), Datius marks your storage as not working. Org admins see a banner in Storage & Credentials and an item in the notification bell, with the reason. Until it's fixed:

New events are refused with 503 and a Retry-After header. The Datius SDK and OpenTelemetry exporters keep them and retry.
Events Datius had already received are held, not dropped, and are written as soon as storage works again.
Reports and the dashboard say storage can't be reached.

Datius never falls back to storing your data somewhere else. Fix the bucket or enter new credentials, then click Test connection (or save the new settings): once the test passes, everything resumes. Datius also retests on its own every few minutes.

Switching and deleting

Changing where data is stored moves what's already there. When your organization has data and you save a new location (from Datius-hosted storage to your bucket, back again, or between two of your own buckets), Datius asks you to confirm, then copies every file to the new location. Storage & Credentials shows the progress.
Ingestion and reports keep working during the move, using the old location until every file is copied; then Datius switches over in about a minute. You can cancel a move before it switches over, and retry one that failed. Storage settings are locked while a move runs.
After a move away from Datius-hosted storage, Datius deletes its own copy after a short grace period. After a move away from your own bucket, the files stay there; remove them yourself if you want them gone.
Only changing the credentials for the same bucket (a rotated key, for example) doesn't move anything; it just has to pass the test.
If your plan changes to one without your own bucket, Datius keeps using the bucket you set up. You can't change it on that plan, but you can switch to Datius-hosted storage, which moves your data as above.
Deleting a signal's data, a workspace or the organization removes the data from Datius but never deletes objects in your own bucket. Remove them yourself if you want them gone.
Retention still applies: if a workspace keeps data for 90 days, older files are deleted from your bucket too.

Something not working? See Troubleshooting.