Skip to content
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

SSH Tunnel and SSL are exclusive #84

Closed
cfroese opened this issue Apr 13, 2018 · 4 comments
Closed

SSH Tunnel and SSL are exclusive #84

cfroese opened this issue Apr 13, 2018 · 4 comments

Comments

@cfroese
Copy link

cfroese commented Apr 13, 2018

For the most part, this exclusion makes sense. However, when use AWS ElastiCache Redis with in-transit encryption means connecting requires a SSH tunnel and then an SSL connection through that.

It would be nice if FastoRedis supported this.

@topilski
Copy link
Member

topilski commented Apr 14, 2018

Hi @cfroese , why you think that EC2 need ssl connection? Here my settings:
default
Where in database path: your AWS ElastiCache Redis url
in ssh: your EC2 instance

for generate public key from pem i used: ssh-keygen -f test.pem -y > test.pub

according this video: https://www.youtube.com/watch?v=AJV5JVLP5lc

@cfroese
Copy link
Author

cfroese commented Apr 14, 2018

Right, I could have described the use case better. I do not need SSL for the EC2 connection. With in-transit encryption enabled for Redis, the connection to Redis must be SSL. The SSH connection with just a pem goes to the EC2 instance to create an SSH tunnel into the AWS environment. Then the SSL connection goes through that tunnel to the Redis cluster.

@topilski
Copy link
Member

topilski commented Apr 14, 2018

I understand you, thanks, will think how to implement it.

@topilski
Copy link
Member

topilski commented Feb 12, 2019

Hi @cfroese , implemented in version 1.24, please check, thank you for the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants