-
Notifications
You must be signed in to change notification settings - Fork 562
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
Support encryption in transit on Memcached cache #8009
Comments
mimir also exposes the same configs. From docs:
Does this solve your problem? |
@dimitarvdimitrov Cool 😎, I've must have overlooked this part. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem?
When introducing more an more data into our Tempo environment, we would like to be on-top of the security. One of these items is the encryption in transit, for the Memcached caches. We host the caches externally (cheaper to have AWS manage them).
The current configuration does not give the ability to have these TLS encrypted connections.
Tempo Cache Configuration
Describe the solution you'd like.
With the latest release of Loki v3.0.0, these changes have also been replicated in Tempo pull request #3585 with the following configuration elements have been added;
This seems to be a perfect solution from my side
Describe alternatives you've considered
Alternatives is to not use TLS for this connection. this is what we are currently doing, and this works perfectly. We are looking into some cost saving (besides the security aspect) and it seems that AWS ElastiCache Memcached Serverless requires the connection to encrypted.
Additional context
`-
The text was updated successfully, but these errors were encountered: