Diagnosing Unexpected Error in Dataflows on initial Set-Up

[Anonymous]

How would you begin to diagnose a unexpected error when you are trying to connect to a databse which is not on premise

I understand you don't require a gateway if the source is not on-premise (i understand its in AWS again not ours another business we are working with). We can connect to this source fine within Power BI Desktop/Power Query

Dataflow Unexpected Error

[Anonymous]

The source is requesting a IP Address (seems thay are using IP whitelisting) to restrict. As dataflows is in the service exactly what IP address would they be refering to??

I've had  a look in this document Download Azure IP Ranges and Service Tags – Public Cloud from Official Microsoft Download Center

and given the IP address for PowerQueryOnline. UK South but that hasnt solved the problem 

[selimovd]

Hey @Anonymous ,

with AWS and Power BI Service it's a little bit more complicated

Did you set the AWS environment up, like described by Amazon with VPC, Subnet and Gateway?

Check the following chapter in the whitepaper on how to do that:

Using Microsoft Power BI with the AWS Cloud - AWS Whitepaper (amazon.com)

Then it should work with AWS.

If you need any help please let me know.

If I answered your question I would be happy if you could mark my post as a solution ✔️ and give it a thumbs up 👍

Best regards

Denis

Blog: WhatTheFact.bi

Follow me: twitter.com/DenSelimovic

[Anonymous]

Thanks Denis

The AWS instance was not set up by us. I gave the Amazon Redshift a go it it stated invaild credentials (which is better than a unexpected error)