-
Notifications
You must be signed in to change notification settings - Fork 3.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Loki uses HTTP for S3 instead of HTTPS #7290
Comments
It seems as though adding (along the These errors disappear, and status codes go from 500 to 200 in /metrics (at However after running for several minutes and accumulating ~ 10k log lines (according to loki_distributor_lines_received_total in /metrics), the bucket is still perfectly empty. When does Loki start using a provided object store in a default configuration? I'd like to ensure it indeed works. |
Eventually started to fill :D I'm leaving this opened and still reiterating the very much not fixed issue, that seems like a bug to fix or quirk to document: Using Additionally specifying |
Hi @Unactived Thanks for reporting this issue. This is definitely something we should improve documentation on, so I add the |
@JStickler - can you please research and assess with @chaudum |
Posting to inform I had the same issue, and that the advice of specifying In my case, I was using ceph-based storage (contabo), and getting 403-unauthorized errors:
|
@GrafanaWriter can I work on this issue ? |
@AlyHKafoury absolutely! It's assigned to me for visibility, but anyone can work on it. |
I traced this from https://github.com/grafana/loki/blob/main/pkg/storage/chunk/client/aws/s3_storage_client.go it seems loki delivers the value correctly it might be a problem with aws sdk version ?. How is the vendor packages managed ? |
Describe the bug
When using the s3 storage backend with an s3-compatible API, Loki (allegedly) attempts to connect to the specified endpoint with an http scheme rather than https, even though
s3_storage_config.insecure
is false.This is an issue for me as the object store I have to use only accepts the https scheme and not http (unrelated to the port).
To Reproduce
Using the official Loki Docker image version 2.6.1, and pushing some logs to it.
Relevant config:
Expected behavior
Loki runs and is able to sync index and chunks on the provided object store through https.
Actual behaviour
Loki tries to use http. Which in my situation correctly results in empty replies.
Environment:
Screenshots, Promtail config, or terminal output
The text was updated successfully, but these errors were encountered: