Sorry if I am stating the obvious, but in many cases using the
S3 gateway is a really good choice, one which many of our users make. End-users need to configure a different S3 endpoint URL and re-use their lakeFS access key ID and secret access key. Then accessing
s3://my-repo/branch/path/to/something.csv will access the path on the specified repo and branch. Since most (all?) tooling supports the S3 API, often switching to lakeFS can require nothing more than configuration.