Connecting to an Amazon DocumentDB Cluster from Studio 3T
If you don’t already have an Amazon DocumentDB cluster running on Amazon EC2, follow the instructions on how to Connect with Amazon EC2.
If you don’t have Studio 3T, .
Connect with Studio 3T
Choose Connect in the top left corner of the toolbar.
Choose New Connection in the top left corner of the toolbar.
Choose the Authentication tab and select Legacy in the drop down menu for Authentication Mode.
Choose the SSL tab and check the box Use SSL protocol to connect.
Choose Use own Root CA file. Then add the Amazon DocumentDB certificate (you can skip this step if SSL is disabled on your DocumentDB cluster). Check the box to allow invalid hostnames.
Note
Don’t have the certificate? You can download it with the following command:
If you are connecting from a client machine outside the Amazon VPC, you need to create a SSH tunnel. You will do this in the SSH tab.
Check the box for Use SSH tunnel and input the SSH address in the SSH Address field. This is your instance Public DNS (IPV4). You can get this URL from your .
For SSH Auth Mode, select Private Key. In the Private Key field, choose the file finder icon to locate and choose the Private key of your Amazon EC2 instance. This is the .pem file (key pair) that you saved while creating your instance in Amazon EC2 Console.
If you are on Linux/macOS client machine, you might have to change the permissions of your private key using the following command:
Note
This Amazon EC2 instance should be in the same Amazon VPC and security group as your DocumentDB cluster. You can get the SSH address, username and private key from your Amazon EC2 Management Console.
Now test your configuration by choosing the Test connection button.
A diagnostic window should load a green bar to indicate the test was successful. Now choose OK to close out the diagnostic window.
Choose Save to save your connection for future use.
Now select your cluster and choose Connect.
Congratulations! You are now successfully connected to your Amazon DocumentDB cluster through Studio 3T.