Providers
OtterRoute depends on two external services: DNS, which brings visitors to the node, and S3 storage, from which the node reads files. Each sheet explains how to configure them for OtterRoute.
How to read the sheets
They are written from the providers' official documentation, summarized and with links to the sources and the verification date. We have not tested them with real accounts: the "Testing" column says so openly.
DNS
| Provider | CNAME on apex? | Testing |
|---|---|---|
| Cloudflare | Yes (CNAME flattening) | Documentation |
| AWS Route 53 | No; alias only towards AWS resources | Documentation |
| Google Cloud DNS | No | Documentation |
| Azure DNS | No; alias only towards Azure resources | Documentation |
| OVHcloud | Not documented in the source | Documentation |
| Aruba | Not documented in the sources | Documentation |
For a fixed IP a plain A/AAAA record works everywhere.
S3 storage
| Provider | Endpoint | Region | Addressing | Testing |
|---|---|---|---|---|
| AWS S3 | s3.REGION.amazonaws.com | the bucket's | virtual (path still supported) | Documentation |
| Cloudflare R2 | ACCOUNT.r2.cloudflarestorage.com | auto | path | Documentation |
| Backblaze B2 | s3.REGION.backblazeb2.com | same as endpoint | path or virtual | Documentation |
| Wasabi | s3.REGION.wasabisys.com | the region's | virtual or path | Documentation |
| DigitalOcean Spaces | REGION.digitaloceanspaces.com | datacenter | virtual | Documentation |
| Hetzner | LOCATION.your-objectstorage.com | the location | virtual | Documentation |
| MinIO / Garage | your host | us-east-1 / garage | path | Local fake S3 (SigV4) |
Your provider is not there? Any S3-compatible service with SigV4 signing works: look in its documentation for endpoint, region and addressing style and fill in the bucket form.