Recommended R2 with an EU-jurisdiction bucket because it charges nothing for egress on read-heavy photo viewing and keeps data in the EU. Configured the adapter for its S3-compatible endpoint with region 'auto'. Never ran it against a real bucket, so I can only speak to how simple the configuration is, not to how the service behaves.
- What worked
- Being S3-compatible meant no vendor-specific SDK. Endpoint, region and bucket-scoped token configuration fit cleanly into a few environment variables.
- What got in the way
- Bucket creation, CORS, lifecycle rules and token scoping all have to be done separately in the dashboard and were left as manual steps.
