Databases hosted on Scalingo are not by default directly available on the Internet. To access it, a solution is to setup an encrypted tunnel.
Robo 3T (formerly Robomongo) lets you configure this tunnel. We will guide through the steps to configure the connection to a Scalingo hosted MongoDB through an encrypted tunnel.
Configuration of Robo 3T
The connection data can be found from the
MONGO_URL environment variable of your
$ scalingo env | grep MONGO_URL MONGO_URL=mongodb://sample-node-meanjs-7093:EsEjseivpacatVoogfijbiapgadTyg@c393a9e3-42fe-4e33-9e6c-8ee815e9af88.sample-node-meanjs-7093.mongodb.dbs.scalingo.com:31312/sample-node-meanjs-7093
In this case:
- Hostname: c393a9e3-42fe-4e33-9e6c-8ee815e9af88.sample-node-meanjs-7093.mongodb.dbs.scalingo.com
- Port: 31312
- User: sample-node-meanjs-7093
- Password: EsEjseivpacatVoogfijbiapgadTyg
- Database: sample-node-meanjs-7093
Fill the fields accordingly:
The “Private key” to provide in the “SSH” tab is your private SSH key you uploaded on your Scalingo profile.
The “SSH Hostname” and “SSH Port” depends on the region your database is deployed on:
- Agora Calycé:
- SSH Hostname: ssh.agora-fr1.scalingo.com
- SSH Port: 22
- 3DS Outscale Paris:
- SSH Hostname: ssh.osc-fr1.scalingo.com
- SSH Port: 22
Validate the configuration and click on connect, that’s it.
Connect with TLS
As a replacement to using an encrypted tunnel to connect to your database, you can make it available on the internet from your database dashboard. You must first force TLS connections.
This is done in Robo 3T under the “SSL” tab:
The “Certificate Authority” is downloadable here.