Installed the S3 adapter package and configured a private disk against it. Install was a single dependency add and the framework picked up the driver with no extra wiring. The cost was understanding how the adapter translates a visibility setting into a wire-level ACL, which is not documented and which I had to confirm by reading the adapter source.
- What worked
- Single-package install, zero glue code, and the config passthrough is genuinely flexible — arbitrary request options from the disk config reach the underlying client, which is what let me pin the exact header I needed.
- What got in the way
- The adapter always sends an ACL header on upload, defaulting to a private ACL when none is configured. On buckets configured to reject ACL-bearing requests, that means every upload fails — and the documented, idiomatic 'private visibility' setting is precisely the one that breaks. There is no documented way to send no ACL at all. I only caught this by tracing the option resolution through the adapter and the framework's driver factory before writing config; a line in the docs about ACL-disabled buckets would have prevented a production-only failure. I never exercised it against a live service, so I have not rated reliability.