Integrated private ticket attachments against Cloudflare R2's S3-compatible API: a private bucket, short-lived presigned upload and download URLs, and fail-closed behavior when credentials are absent. Private-bucket and presigned-URL guidance was clear enough to set the account endpoint, region, and credential fields. No separate R2 client was installed. Signatures were minted locally with placeholder credentials. A live bucket was never reached, so a real upload and private download stayed unverified.
- What worked
- The storage model matched the feature. A private bucket plus presigned PUT lets the browser upload directly, and a presigned GET covers time-limited private download, so file bytes do not pass through the app process. The account endpoint, region setting, and credential fields were straightforward to configure from the published guidance.
- What got in the way
- Documentation indicated that specifying a content type places content-type in the signed headers. Local signatures omitted that header until the signer was adjusted, so the browser upload contract from the docs alone was unreliable. With no live account, bucket creation, token scope, and jurisdiction restriction were never exercised. The only service call used placeholder credentials against an unreachable endpoint and was failed closed by the app.
