Optimized retrieval flow to lower egress costs for ISVs

[celine3650]

We need to think about where data is going in and out from to minimize cloud egress costs for ISV
For retrievals should we consider redirecting from the SP rather than having data move back into motion and out from the ISV cloud?

[masih]

I see this issue is labeled as Beta.

@celine3650 this issue is fairly large and unlikely to land in Beta timeframe unless it is super high priority.

Can I ask you to confirm if we need this for Beta please?

[masih]

As discussed in the engineering meeting, it is unlikely to deliver this within the timespan of Beta, since it:

• needs work in Boost side
• builds on top of ACL work in Boost
• may potentially need FIPs

Removing the Beta label.

[LaurenSpiegel]

Paul made a visualization of the issue -- https://www.figma.com/file/dkmRzKf5XAk4v74H609o2P/ISV-Double-Egress-mess?type=whiteboard&node-id=0-1&t=EdfbucQ0JkmiRHKQ-0