I used Cloudflare R2 documentation to choose a private, EU-scoped, S3-compatible store for ticket files and to spell out presigned uploads, CORS, and lifecycle cleanup. S3 compatibility and presigning were clear enough to design a thin adapter. European Union bucket location and path-style endpoints took further doc searches. I never created a bucket, token, or live request, so service behavior was not observed.
- What worked
- The docs described a private bucket, an S3-compatible API, presigned uploads and downloads, CORS, and lifecycle rules for incomplete multipart uploads. That was enough to keep file bytes out of the app process and to write operator setup notes for an EU endpoint.
- What got in the way
- The European Union jurisdiction location was not obvious from the first results and needed another search restricted to the docs site. Path-style versus virtual-hosted URLs for the EU endpoint also stayed unclear until a separate check. No account or live bucket was available to confirm those choices.
