Don't miss your chance to take exam DP-600 or DP-700 on us!
Request nowLearn from the best! Meet the four finalists headed to the FINALS of the Power BI Dataviz World Championships! Register now
While configuring Athena connection details in ODBC using an Athena driver, there is an option to specify AWS S3 bucket location. Connection is successful and we are able to refresh the reports.
Need a few details about this S3 bucket.
1) What is the use of this bucket?
2) Our reports are schduled to be refreshed once a day and on-demand refreshes could be upto max 5 times a day. Does each such refresh use this S3 bucket?
3) What should be the retention period of this bucket?
4) This bucket was created on May 9, 2024 and these are the metrics. Should I be concerned about the total bucket size?
5) Can objects be cleaned up on a daily basis?
6) What other measures do we need to take to ensure that we are not over using the S3 resources?
7) Any other tips and pointers would be of great help.
Solved! Go to Solution.
Hi,@coolsandeee
I am glad to help you.
According to your description, you need a few details about AWS S3 bucket?
If I understand you correctly, then you can refer to my solution.
An S3 bucket is a storage container provided by Amazon Web Services (AWS) for storing objects (files, data, etc.). It’s commonly used for various purposes, such as hosting static websites, storing backups, serving media files, and more.
It is used by every report refresh (Scheduled refresh or on-demand refresh) that sets up S3 bucket. When we refresh the report, it will fetch the data from S3 bucket and process it.
To avoid overuse of S3 resources, we can optimize data storage, use appropriate storage classes, reduce the number of refreshes, and so on.
For more specific and detailed information, you can go to consult Amazon's official senior technical support engineers or after-sales customer service.
I hope my suggestions give you good ideas, if you have any more questions, please clarify in a follow-up reply.
Best Regards,
Fen Ling,
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Thank you for the details, @Anonymous
So, when a refresh is initiated, Athena queries get executed. Is the resultant data and metadata stored in the specified S3 bucket and then the Power BI Service retrieves data from this S3 bucket?
Hi,@coolsandeee
Yes, your understanding is correct. And the whole process is encrypted and secure.
I hope my suggestions give you good ideas, if you have any more questions, please clarify in a follow-up reply.
Best Regards,
Fen Ling,
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Hi,@coolsandeee
I am glad to help you.
According to your description, you need a few details about AWS S3 bucket?
If I understand you correctly, then you can refer to my solution.
An S3 bucket is a storage container provided by Amazon Web Services (AWS) for storing objects (files, data, etc.). It’s commonly used for various purposes, such as hosting static websites, storing backups, serving media files, and more.
It is used by every report refresh (Scheduled refresh or on-demand refresh) that sets up S3 bucket. When we refresh the report, it will fetch the data from S3 bucket and process it.
To avoid overuse of S3 resources, we can optimize data storage, use appropriate storage classes, reduce the number of refreshes, and so on.
For more specific and detailed information, you can go to consult Amazon's official senior technical support engineers or after-sales customer service.
I hope my suggestions give you good ideas, if you have any more questions, please clarify in a follow-up reply.
Best Regards,
Fen Ling,
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Share feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.
Check out the February 2026 Power BI update to learn about new features.
| User | Count |
|---|---|
| 54 | |
| 45 | |
| 38 | |
| 16 | |
| 15 |
| User | Count |
|---|---|
| 86 | |
| 70 | |
| 38 | |
| 29 | |
| 26 |