Connect PostgresSQL db using SSH Tunnel

Matillion ETL
1

I have been trying to connect to a Postgres db in a AWS EC2 instance using SSH Tunnel.

How can i do that for connecting my db as a source?

Would love some help with this

2

Hi

 

have you followed below steps;

 

Create data base connection from manage option

PostgreSQL as the database type.

With details like hostname, port, username, and password.

Check the box that says "Use SSH Tunnel."

Enter the AWS EC2 instance's public IP or DNS as the SSH hostname

Set the SSH port to 22

Type in your SSH username

Choose the SSH key pair you used

Test —> Save —> Use

3

Where exactly is manage options? I have been trying to build this using the orchestration pipeline feature.

4

is this within dataloader or somewhere else?

5

Where you able to figure this out in the Data Productivity Cloud? I'm trying to do the same thing.

6

Hi! I am with a company called Progress and we have a great solution to securely connect Matillion to on-premises databases using our data gateway. It allows for secure HTTPS access from Matillion to your database. We have current Matillion customers using it to solve this problem. This tutorial covers the process:

https://www.progress.com/tutorials/cloud-and-hybrid/integrate-on-premises-data-into-matillion-etl-using-progress-datadirect-hybrid-data-pipeline

I would be happy to answer any questions on this - aburg@progress.com

Thanks

Aaron

7

Hi @knorman​ ,

I work for the Matillion Product Team and right now the Data Productivity Cloud does not support SSH tunnelling to PostgreSQL databases but this is something I'm looking into at the moment. Actually - my remit is wider and I'm looking about how we can improve security and connection options across both our Full SaaS and Hybrid SaaS offerings.

As such I'd love to speak to you on a call if you can spare some of your valuable time - I'd like to understand what you're using the Data Productivity Cloud for and your setup at a high level.

I'll reach out via email - and hopefully we'll speak soon.

Many thanks,

Jamie Cole (Product Manager)

8

We shifted to a hybrid set up with agents installed in our AWS environment and reconfigured our project. Problem solved.

9

Happy to have a discussion.