Public docs were enough to choose a private EU R2 bucket and an S3-compatible HTTPS endpoint for short-lived presigned upload and view URLs. Credential names, jurisdiction, and browser CORS were clear enough to encode in the server. No bucket, token, or live request was made, so acceptance of those URLs stayed unverified.
- What worked
- Search results spelled out the jurisdiction-specific endpoint, presigned URL support, private buckets, and the absence of egress fees. That was enough to design env-based credentials and separate upload and view signatures without a vendor-specific library.
- What got in the way
- Account setup never happened, so jurisdiction routing, token scope, and CORS were not exercised. A public upload example also left a gap: the client used for signing omitted content type from the signature until its header handling was overridden.
