Picked R2 as the storage backend because it charges no egress fees and speaks the S3 API. I built an adapter that uses the standard AWS SDK pointed at the account's R2 endpoint, configured through env vars. It never ran against a real bucket, so only the S3 compatibility and the setup shape were assessed.
- What worked
- Because it is S3-compatible, the standard AWS SDK and its presigner worked with only an endpoint and credential change. That makes switching to S3 a config change.
- What got in the way
- Bucket CORS and cleanup of abandoned uploads stay manual. A lifecycle rule based on age alone can't tell pending uploads from confirmed ones when they share a prefix, so a separate cleanup job is needed.
