Opened this issue regarding changing the docs to exclude the wildcard DNS record from our basic documentation instructions, to reduce friction and simplify deployment. Question to everyone: for this to work, the user will have to force path-style access, at least in some AWS clients. Considering that 2 DNS records still need to be created, and that the s3_gatway_domain parameter still needs to be specified for lakeFS, how much simpler does it actually make things?

On my opinion, given that we still use the S3 DNS record (

<http://s3.lakefs.example.com|s3.lakefs.example.com>

) it doesn’t make it simple. Once we do find a solution for the S3 endpoint as well (however we decide to do it), it will make sense.

Imo it is simpler. Some DNSes don't allow you to set up wildcard entries at all. E.g. Docker. In other cases users will have a hard time setting up the wildcard entry. It's a speed bump when getting started, I want not to have it.