User Profile
GauravSinghPBI
Helper III
Joined 1 year ago
User Widgets
Contributions
Re: Power BI (Azure-hosted SaaS service) to AWS S3 via Athena Connectivity
v-sshirivolu Thanks for the reply. We are not storing the credentials in On-Premise Data Gateway instead we have managed to use the credentials directly in Power BI Service using OBDC String. Is there any automated way to update the AWS IAM user keys and passwords directly in Power Bi service using some script etc. Thanks, Gaurav682Views0likes1CommentRe: Power BI (Azure-hosted SaaS service) to AWS S3 via Athena Connectivity
v-sshirivolu Thanks for the response. One challenge - We are going to reset the IAM user keys and password every 90 days using release process and login to AWS and use those keys/password in Power BI ODBC connection. This is repeatable process and has to be done every 90 days. Is there any automated way to reset the Keys and password automatically using some python script or any other means. Thanks, Gaurav723Views0likes3CommentsRe: Power BI (Azure-hosted SaaS service) to AWS S3 via Athena Connectivity
Thanks v-sshirivolu for the response. We are able to fetch the data in Power BI Service using "GetQueryResults" instead "GetQueryResultsStream" option without opening 444 port. Few question still arises, Kindly check --> 1. Import mode we probably dont care and wont need 444, with a direct query route from users we might want the stream? 2. what is the protocol the driver uses on 444. Is it https? If not does it transfer any business data or does it only have metadata that somehow facilitates encrypted business data streaming on 443? Either would be ok - as long as there is no business data transferred in plain text 3. Is there any difference in using "GetQueryResults" instead "GetQueryResultsStream" from performance or connection or any thing else prespective? Thanks, Gaurav844Views0likes5CommentsRe: Power BI (Azure-hosted SaaS service) to AWS S3 via Athena Connectivity
Thanks v-sshirivolu for the response. I am able to fetch the data in Desktop using DSN defined in ODBC installed on my desktop and with whole connection string also which is defined in Power BI Service. Do you still think we don't need 444 port for On-Premise Data Gateway to AWS Server? Thanks, Gaurav879Views0likes7CommentsRe: Power BI (Azure-hosted SaaS service) to AWS S3 via Athena Connectivity
Hi v-sshirivolu We are connecting to Power BI Service to On-Premise Data Gateway to AWS S3 Bucket using ODBC Driver installed on On-Premise Data Gateway. We are using ODBC String in Power BI service - ODBC connection to connect to AWS. We are not getting confirmation whether we need both (443 and 444) port to be opned from On-Premise Data Gateway to AWS Server. Question 1)As per below documentation, Port 444 is needed for ODBC driver. Could we know why it is needed and if any data travels on the connection and if so what protocol? https://docs.aws.amazon.com/athena/latest/ug/odbc-v2-driver.html 2) Why 443 is needed to be opened? Thanks, Gaurav2.4KViews0likes10CommentsRe: Best way to Load-Transform-Cache for Power BI Report fetching data from AWS S3 Bucket
Thanks cengizhanarslan for the response. I can check whether our premium workspaces are Fabric capacity (F-SKU) and Pro ones obviously not. We are thinking to create Semantic Model within Premium and share to prower users who will sit in Prod Workspace to create report using it. Question - Related to Lakehouse, Dataflow and Semantic Model - what are the functionalities which won't be available in Pro Workspace w.r.t Premium capacity. For ex. creation of Lakehouse and dataflows, scheduling frequency, deployment pattern etc737Views1like1CommentBest way to Load-Transform-Cache for Power BI Report fetching data from AWS S3 Bucket
We want to connect from Power BI within Azure to AWS S3 Bucket using ODBC DSN and want to populate the Power BI cache which can be used for reports to use. We will be combining multiple tables including dimension and facts along with some transformations having million of rows in target result set which will be kept in cache. We will be having two types of power BI roles which will be used for data level security. We should be able to handle incremental refresh daily in Semantic Model cache. We are thinking of having of two approaches given below. Which one is the best way to handle this or if there is any other method which we can follow 1. Should we create separate Semantic Models and combine multiple tables and fetch the data ftom AWS S3 bucket incremenatally daily and populate the cache and report should display the latest data from these SMs? 2. Should we create a Lakehouse and create x2 gen2 dataflows within that, which will populate x2 tables and I can see them in the Lakehouse editor then I can create a semantic model (which is based on the lakehouse) and a report based on the semantic model I think with this approach we are just using the dataflows as an ETL and we have good transparency on the data in the lakehouse (including ability to query in SQL) and the SM against the lakehouse seems to work nicely.Solved828Views0likes7CommentsRe: Power BI (Azure-hosted SaaS service) to AWS S3 via Athena Connectivity
Thanks v-sshirivolu for the response. Our Data Gateway is not on AWS instead on Internal Cloud. How the Rotation thing can be handled automatically or if there is any option of permanent keys? On second question - Obviously the use of the connection itself at runtime won't be under BG. We are talking about a way to enter the username and keys into the power bi service as a one-off admin setup so they are not in the dsn.1.3KViews0likes0Comments
Data Privacy
Microsoft Fabric Community and Privacy
To learn more about how we manage your data, please review the Microsoft Fabric Community Data Privacy guide.