Unable to connect to AWS RDS postgres via Cloud connection OR personal gateway

[mkp88]

I want to setup refresh for reports using AWS RDS postgresdb and after following some steps (re. aws certificate, npgsql etc.) I was able to connect to it from desktop but when I publish it in service, it only shows an option to configure cloud connections and not gateway which I guess is because a direct postgres connection is possible and does not require gateway.  But then when I try to add connection by providing credentials it doesn't connect !  Not sure what am I missing here? I need help with below queries:

1) If I dont need a gateway for this, then why am I not able to connect and what do I need to do ?

(the error while trying to establish a cloud connection is : A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond')

2) If using gateway is an option too, I tried with a personal gateway first, but it didn't appear as an option , I see other enterprise gateways available but not my personal gateway through which I wanted to try connecting first.  Why I dont see my personal gateway to configure, even though its online and available?

PS: I have gone through all existing related posts but none of them seem to help with above issue.  I have already tried the certificate, npgsql etc. related steps shown.  Only thing pending to try is via the enterprise gateway (not personal) which is pending npgsql as I don't directly control that server.  But before that I would like to see why above options won't work!

[v-echaithra]

Hi @mkp88 ,

Thank you for the update and for letting us know the issue has been resolved.

If you have any new questions or topics, don't hesitate to start a new thread in the Microsoft Fabric Community Forum. We're here to assist you.

Thank you for being an active member of the Microsoft Fabric Community!

[mkp88 · Accepted solution]

An update, I got it working using the enterprise gateway after resolving some firewall issues (also installing npgsql and certificates etc.), but it still didnt work via a direct cloud connection I guess because app.powerbi.com doesn't have a static IP, although I found a range of IPs that powerbi online uses but at present isn't feasible to whitelist all of them or even periodically keep it updated as and when MS updates it.

[ibarrau]

Hi. Just because i'm not sure if you have found this article, this one helped me to make it work. 

https://blog.ladataweb.com.ar/post/187904496250/conectar-power-bi-a-rds-postgres-en-aws

I have used an on premise data gateway in enterprised or standard mode in an EC2 aws vm.

I hope that helps,

[mkp88]

Thanks, yes I already checked that link earlier and its only about pbi desktop, which I am able to connect.  Problem is from service.

[ibarrau]

Have you configured that exact thing in an EC2 VM with a Enterprise or Standard mode for the gateway? That thing in the post is what you need to do in the gateway vm too. After configuring, restart and try.

I hope that helps,

[mkp88]

That part is in progress, although I dont have an EC2 VM, and I guess it shouldn't matter as the gateway can be on any machine right.  But I do have a personal gateway on my pc and have configured all those things to try that myself before the changes in production gateway server, but the thing is I dont see the option to configure a connection via personal gateway as shown in my original post.   

[ibarrau]

You won't find it. personal mode doesn't work like that. We could say Personal mode is not the same gateway. It's kind of a different tool. It's a regular app. The standard is a windows service connected to power bi service in a better way. If you want to work with environments I still recommend standard gateway. Personal it's really just for one person to test stuff or specific requirements.

I hope that helps,

[mkp88]

Ok I understand the limitations of personal gateway like its for one user, doesn't work with directquery etc. but I didnt find anywhere that it cannot connect to some databases or like in my case I dont see any specific reason of why I could not even use to test it before configuring the similar options on enterprise gateway server.