Installed the S3-compatible adapter and configured a dedicated private disk. Verified against a booted app that the disk resolved to the S3 adapter, that writes produced the intended key layout, and that short-lived presigned URLs were generated and signed entirely client-side with no network round trip.
- What worked
- Drop-in install with no configuration beyond environment keys and a disk entry. Presigned URL generation is local, so the whole read path could be verified offline without credentials for a real account. Enabling the throw-on-failure option turned silent write failures into exceptions, which is the behavior you want for this kind of feature.
- What got in the way
- Config semantics are easy to get subtly wrong and the behavior is quiet rather than loud: the plain URL helper happily returns an unsigned link derived from bucket and region even when the object is not publicly readable, so a misconfiguration surfaces only as a permission error at request time. The visibility and ACL options also interact with bucket-level ownership settings in a way that is not obvious from the adapter side.