This is less of a question on who may have some experience in this area (although such would be highly appreciated), as much as a sanity check, maybe stemming from not enough understanding on how some of these pieces could function together, but still seeing an opportunity in it.
Details: merger btw two different organizations, each with its own SD-WAN solution, one having a heavy on-prem hosting presence, combined with AWS hosting, on path to a multi-year migration from on-prem to AWS activity, while the other having largely AWS hosted stuff, plus some other SaaS, and both having either DXs or VPNs, tied into their own SD-WANs, in diff parts of the world. Little needs to have the two networks "see" each other (critical point in what follows)
Options:
- migrate the smaller footprint SD-WAN technology into the bigger SD-WAN (rip and replace), for universality of solution, for global traffic management, even if not necessarily fully meshed (possible through either SD-WAN solution policy)
or
- use AWS TGWs to "tie" the two SD-WANs together, with common legs into TWGs, maybe in different regions. This is the alternative I need to do more research on, but feels more flexible, for such events (M&As, followed by integration). Do you see anything wrong with this? Traffic patterns and evaluation of associated costs, if to end up with a lot more traffic across AWS, will definitely be conducted, but it "feels" like with some independence between the two organizations, as limited access needs btw on-prem A to on-prem B (except for integrating management, of course, until all this is also AWS hosted), this may not end up in such a bad situation.
No comments:
Post a Comment