-
Notifications
You must be signed in to change notification settings - Fork 500
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
new feature: Memcached In Transit Encryption (TLS) support #5419
Comments
Hello, I would like to contribute to the development of this feature. Could you tell me which part of the code I should read , or provide some other relevant information? @Xuanwo |
Hi, @ozewr, thank you for your interest! Memcached currently interacts directly with opendal/core/src/services/memcached/binary.rs Lines 104 to 109 in f0ace56
We need to add support for using a TLS library like |
Hello, I'm a new programmer, so I want to share my thoughts and see if they are correct. It seems that here we need a new struct implementing bb8::ManageConnection, similar to MemcacheConnectionManager. However, impl bb8::ManageConnection for MemcacheConnectionManager {
type Connection = TlsConnection { io: BufReader<TlsStream<TcpStream>> };
type Error = Error;
... Or directly modify the implementation of bb8::ManageConnection for MemcacheConnectionManager to make it only support TLS connections. @Xuanwo |
Maybe we can make |
@Xuanwo I wanna take up this task. |
Sorry, I’ve been a bit busy with my day job this week, but I think I should be able to submit a PR tomorrow. I think we can collaborate on it. @geetanshjuneja |
Feature Description
AWS Elasticache Memcached serverless instances require using TLS,
meaning that instead of doing
telnet ....cache.amazonaws.com 1211
you doopenssl s_client -quiet -crlf -connect ....cache.amazonaws.com:11211
, supporting this TLS mode here would be great :)Problem and Solution
Adding TLS support, See: https://docs.aws.amazon.com/AmazonElastiCache/latest/dg/in-transit-encryption.html
Additional Context
No response
Are you willing to contribute to the development of this feature?
The text was updated successfully, but these errors were encountered: