Closed jpds closed 1 year ago
That's a bug for @trinity-1686a :D
Hi @jpds
I'm not able to reproduce this issue with Deuxfleurs Garage cluster. By default, Quickwit tries to use vhost style when interacting with S3. Garage supports vhost style too, but you need a wildcard DNS entry to use that (CNAME *.s3.example.com => s3.example.com
). Can you check if you have such an entry, or at least one for qw-test.s3.example.com
? If you can't create such a DNS entry, you should indeed use QW_S3_FORCE_PATH_STYLE_ACCESS=true
wait, force_path_style_access: true
is already set in the configuration, so there is indeed a bug there, the environment variable shouldn't be required :confused:
Closed via #3583.
Describe the bug
I just tried using Quickwit locally on my laptop pointing at a remote Garage installation, and with the following configuration:
With this, it would simply return:
I was only able to make it work after setting:
However, I'd expect it to detect the custom endpoint without setting the environment variables.