-
Notifications
You must be signed in to change notification settings - Fork 354
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
[QUESTION]TLS support for AWS Elasticache Cluster #332
Comments
Sorry, but test_redis++ does not work with TLS. You can write a simple code to do the test (check README for code example). Do not forget to specify certificate file related info. Regards |
Thank you @sewenew , I checked the test code and found it doesnot contain TLS code. Tried the sample code, but met the following errors. The TLS needs certificate, but I am thinking it does not suit for Elasticache since the password is used instead of certificate. I saw a similar question here, but not sure if this is resolved. Thank you!!! /usr/local/lib/libredis++.a(connection.cpp.o): In function |
Looks like you did not link hiredis_ssl. In order to use TLS, you should link both hiredis and hiredis_ssl:
So far, hiredis does not support skipping certificate verification. Since redis-plus-plus is based on hiredis, so it still needs a certificate file. Check this for detail. Once hiredis has support for skipping certificate verification, redis-plus-plus will automatically support it. It seems that hiredis has not fix it yet (there's a PR to fix the problem, but not merged yet). Also, you might want to try the stunnel solution mentioned here. So that you don't need to make the client support TLS. Regards |
Thanks a lot, got you!
Elasticache is using Auth/Password instead of certificate since its source is a reliable. I like to check if the Auth is supported by the RedisPlusPlus since I saw some hiredis examples are listed with Auth instead of certificate. |
If hiredis already has the support, redis-plus-plus should work too. Since it's based on hiredis. Not sure if the example might use stunnel solution as I mentioned above. Regards |
Samples from redis offcial https://docs.redis.com/latest/rs/references/client_references/client_c/ and huawei site https://support.huaweicloud.com/intl/en-us/usermanual-dcs/dcs-ug-0312010.html ,and they doesnot mention stunnel. |
Since there's no update, I'll close this issue. Regards |
Describe the problem
We are using Redis Cluster in AWS Elasticache and trying to access it with redis-plus-plus. Now non-auth(TLS) cluster is accessed successfully, but auth cluster is failed to connect. It is handing there and without any errors, the command is "./build/test/test_redis++ -a *** -n clusterhost -c 6379". Any hints here, thank you!
During building the hiredis, we open TLS support as mentioned in the Readme.
hiredis:
make USE_SSL=1
make USE_SSL=1 install
redisplusplus:
cmake -DREDIS_PLUS_PLUS_USE_TLS=ON -DREDIS_PLUS_PLUS_CXX_STANDARD=17 ..
make
make install
Environment:
The text was updated successfully, but these errors were encountered: