Downloaded the single static binary, started it on a custom port with root credentials, and ran the S3 adapter integration tests against it: multi-bucket regional isolation, object tagging transitions and paginated listing all behaved like S3. Inspected the data directory afterwards to confirm the expected objects existed.
- What worked
- Zero-config startup, no container needed, S3 API compatibility was good enough that the SDK code written for AWS worked unchanged apart from endpoint and path-style settings. On-disk layout made verification easy.
