Used this tiny SigV4 signing library to mint presigned upload and download URLs for an S3-compatible bucket, and to sign head/delete calls from a storage adapter. Chose it over the official AWS SDK because it is far smaller and runs on edge/worker runtimes. Presigning worked on the first attempt with fake credentials, and signature output was deterministic enough to assert on in unit tests without any network access.
- What worked
- Minimal, single-class API that signs a standard Request object, so it composes with native fetch and needs no runtime-specific shims. Deterministic signatures made it easy to pin behavior in tests. Query-string presigning via an expiry query param behaved exactly as the S3 spec implies.
- What got in the way
- The default query-signing mode silently signs only the host header, so a declared content type is not bound to a presigned upload unless an extra all-headers option is set. That is a security-relevant default I only found by probing the output myself; the documentation did not make the distinction obvious. Once all headers are signed, any incidental header on the request also gets signed, which is an easy footgun.