Connecting Cloud WAN with Kong and MegaPort

Connecting Cloud WAN with Kong and MegaPort An architecture diagram generated by Archify. Konnect Control Plane · Kong-managed SaaS · Architecture component Konnect Control Plane Kong-managed SaaS Kong Data Plane · self-managed Hybrid DP · AWS US Region › AWS Cloud WAN · network edge Kong Data Plane self-managed Hybrid DP network edge VPC: App / Service A · AWS US Region › AWS Cloud WAN VPC: App / Service A VPC: App / Service B · AWS US Region › AWS Cloud WAN VPC: App / Service B Megaport · Megaport Cloud Router · Architecture component · multi-VPC hub Megaport Megaport Cloud Router multi-VPC hub Kong DCGW · Azure US (abstracted) · Azure US (abstracted) Kong DCGW Azure US (abstracted) Kong DCGW · Japan AWS (abstracted) · Japan AWS (abstracted) Kong DCGW Japan AWS (abstracted) outbound mTLS :443 private interconnect (bidirectional) via Megaport via Megaport AWS US Region AWS Cloud WAN Azure US (abstracted) Japan AWS (abstracted) Legend Backend Cloud External

Cloud WAN as the network

  • • AWS Cloud WAN groups all VPCs in the AWS US region
  • • Only the Kong DP VPC is treated as the network edge
  • • App VPCs A/B stay reachable via Cloud WAN, no Megaport attachment needed

Kong-to-Kong over Megaport

  • • Megaport interconnect replaces Transit Gateway entirely
  • • The Data Plane <-> Megaport link is bidirectional; Megaport fans out to multiple remote regions/VPCs
  • • Two remote regions shown here: Azure US and Japan AWS, each abstracted behind its own Kong DCGW

Deployment model trade-off

  • • This Kong DP is self-managed Hybrid, not a Konnect Dedicated Cloud Gateway (DCGW)
  • • DP keeps only outbound mTLS to the Konnect Control Plane, no special network attachment kind required
  • • Falls outside Konnect's uptime SLA -- customer owns HA, patching, and scaling for this DP