zeekayandHanzo Dev ede6abec36 s3: run on Hanzo Storage through hanzos3/go, not the AWS SDK ...

vfs was the last service reaching S3 through github.com/aws/aws-sdk-go-v2 while
the rest of the fleet (vm, commerce, licensing, ai) already used the Hanzo
Storage Go SDK. Both speak S3, so either works against our own storage — but a
second client meant a second credential model, a second retry policy, a second
error taxonomy, and ~30 extra modules in the graph for a backend that makes
five calls.

The SDK also moved orgs on the way in: github.com/hanzoai/s3-go is now
github.com/hanzos3/go. hanzoai/* is for top-level products; a product's own SDK
belongs in that product's org, which zap-proto/{go,zip,http} and hanzo-ds/go
already do.

Every aws-sdk-go-v2 module is gone from go.mod. The endpoint still comes from
the URL's `endpoint` parameter or AWS_ENDPOINT_URL, defaulting to Hanzo Storage.
One behavioural note: this SDK's GetObject is lazy, so a missing key surfaces on
the first read rather than on the call — backend.ErrNotFound is mapped in both
places so callers still see one sentinel.

Co-authored-by: Hanzo Dev <[email protected]>

2026-07-27 12:20:32 -07:00

..

s3.go

s3: run on Hanzo Storage through hanzos3/go, not the AWS SDK

2026-07-27 12:20:32 -07:00