Forum Discussion
Shortcut to AWS S3 - AWS Data Transfer Costs
- 1 year ago
Copy the data once to OneLake / Azure.
After that, use incremental loads to transfer only daily changes instead of the full 200 GB.
Partition your data so Fabric reads only the required portion.
For permanent, heavy workloads, move the dataset entirely to Azure to avoid ongoing egress costs.
If this helps, consider giving some Kudos. If I answered your question, please mark this as the solution.
- 1 year ago
Hi MelisandeRicou,
-
A shortcut does not copy data, it streams it from S3.
-
On-demand reads trigger AWS S3 egress (billed as “DataTransfer-Out-Bytes”).
-
Caching in Fabric can reduce repeated egress
Thank you for your patience and look forward to hearing from you.
Best Regards,
Prashanth Are
MS Fabric community support -
May I ask if you have resolved this issue? If so, Can you please share the resolution steps here. This will be helpful for other community members who have similar problems to solve it faster.
If we don’t hear back, we’ll go ahead and close this thread. For any further discussions or questions, please start a new thread in the Microsoft Fabric Community Forum we’ll be happy to assist.
Thank you for being part of the Microsoft Fabric Community.