Connecting to a RDS Server from a Local Computer Using SSH Tunneling on a Mac

18 thoughts on “Connecting to a RDS Server from a Local Computer Using SSH Tunneling on a Mac”

  1. It would be the same way your normally ssh into your server. For example on this site, I ssh in with

    sshusername@thekeesh.com

    Similarly, you could do it with an IP address or some other name

    sshuser@YOUR IP

    or amazon often will give you a longer public dns name.

  2. Thanks for this article, Jeremy. I was having difficulty getting tunneling to work on my own, but switching from localhost to 127.0.0.1, as you suggest in this article, did the trick. I really appreciate that you wrote this out.

  3. Hi,
    Thank you for this post. It saved me from alot of pain. in case one uses a key then make sure u add the -i option

    ssh -N -L 3307:RDS_HOST:3306 USER@AWSHOST -i KEY

    and also once connected it will just blink so u need to open a new terminal to query the db

    Thanks,
    Vishal

  4. Hi Vishal,

    “and also once connected it will just blink so u need to open a new terminal to query the db”

    My Terminal is just blinking now after doing this:

    ssh -N -L 3307:RDS_HOST:3306 USER@AWSHOST -i KEY

    How now do I add the second part?

    mysql -u dbuser -p -h 127.0.0.1

    What are the steps to open a new Terminal to query the db?

    Thanks

  5. I’m not sure where the tunneling comes in but I usually just log into my EC2 Instance as you would normally do and then issue a mysql connect to the endpoint.

    That has worked for me.

  6. Thank you! This saved me the trouble of re-creating my RDS server, migrating, etc. which would have resulted in 30 minutes of downtime and a late night for me!

  7. Hey guys,

    For the people who are using nodejs. Use my working code as an example:

    //AWS Configuration file
    RDS : {
    host : ‘127.0.0.1’,
    database : ‘*****_db’,
    user : ‘*****’,
    password : ‘*****’,
    port : ‘1234’
    },
    RDSWithoutTunneling : {
    host : ‘your.rds.endpoint.rds.amazonaws.com’,
    database : ‘*****_db’,
    user : ‘********’,
    password : ‘********’,
    port : ‘3306’,
    }

    //Controller file.

    AWSConfig = require (‘../config/aws_config.js’);
    function getConnection(){
    var connection = mysql.createConnection({
    host : AWSConfig.RDS.host,
    database : AWSConfig.RDS.database,
    port : AWSConfig.RDS.port,
    user : AWSConfig.RDS.user,
    password : AWSConfig.RDS.password
    });
    return connection;
    }

    //Implementation (Steps)

    – Using ssh tunneling :
    1. In a terminal run: ssh -N -L 1234:your.rds.endpoint.rds.amazonaws.com:3306 -i Keypem.pem ubuntu@xx.xx.xx.xx
    2. In another terminal run: mysql -u admin -p -h 127.0.0.1 -P 1234

    – Not using ssh tunneling:
    1. Add your IP address to a whitelist on RDS Security Group.
    2. Make sure when you create your RDS instance that ‘publicly accessible?’ is ‘yes’. If not, you won’t be able to connect even when you have the ports properly set up.

    Hope this is useful for you.

  8. Sorry, I don’t get it! SSH usually requires a password or ssh key to be given by the server and installed on the client. There is no mention of passwords or ssh keys in your article. So where do I get mine? I don’t see anywhere on the AWS Console to retrieve it.

      1. RDS doesn’t know that the tunneling is taking place. The mysql command line client is connecting directly to RDS via an ssh tunnel. This definitely works. Regarding keys, ssh assumes a default key or you can specify a key with the “-i” flag as described by another poster above.

      2. The ssh key is the key you would normally use to connect to an EC2 server. If you don’t know how to set that up, you will need to turn to AWS documentation. It is simple.

    1. I agree. Something is missing here. Although even some of AWS documentation do not touch on pw or ssh keys either. Its hard to believe that people are connecting to AWS databases with data passing through internet in clear view.

  9. Many thanks for this article – I went through it, and to my surprise, everything worked right the first time. (Not used to that happening…)

    I thought I’d also reply to Josh, maybe this will clarify what’s going on with tunnelling. He’s correct that Amazon does not allow *direct* SSH access to RDS instances. Likewise, Glen is correct that you can login to an EC2 instance that is in the same VPC, and from there, SSH into the RDS instance. But that can be a pain – tunnelling lets you connect from your local laptop directly to RDS. Josh was asking about the SSH keys – those need to be downloaded from AWS (and installed on the EC2 instance at launch). Then you can either configure it in the SSH config file, or use the ssh -i key.pem option. The config file is:

    ~/.ssh/config
    Host east_fubar
    Hostname 52.87.123.123 # EC2 instance
    User ubuntu # depends on the AMI – might also be ec2-user/cloud-user, etc
    IdentityFile /home/fubar/.ssh/ec2_key.pem # This key is from AWS, and is on the EC2 instance

    ssh ubuntu@east_fubar # Once you can do this, should be able to tunnel:

    This says, “ssh into this EC2 box as this user – then any packets on that port, pass-through to the RDS server”
    ssh -N -L 1234:fubar.us-east-1.rds.amazonaws.com:3306 ubuntu@east_fubar
    mysql -u db_admin -p -h 127.0.0.1 -P 1234

    So you are not *directly* ssh’ing into the RDS box, but instead an EC2 box, which passes on the packets to RDS.

Leave a Reply