From 59b7ac0f46941d534e895bce3d6958b683f1267f Mon Sep 17 00:00:00 2001 From: Henry Mollman Date: Fri, 30 May 2025 09:57:40 -0700 Subject: [PATCH] Make explicit that TCP traffic is not supported --- cloudhub/modules/ROOT/pages/vpc-upgrade.adoc | 8 +------- 1 file changed, 1 insertion(+), 7 deletions(-) diff --git a/cloudhub/modules/ROOT/pages/vpc-upgrade.adoc b/cloudhub/modules/ROOT/pages/vpc-upgrade.adoc index 69c4bc49f..c2085ffbf 100644 --- a/cloudhub/modules/ROOT/pages/vpc-upgrade.adoc +++ b/cloudhub/modules/ROOT/pages/vpc-upgrade.adoc @@ -53,13 +53,7 @@ CloudHub VPC doesn't restrict outbound egress traffic, so removing the default f Non-HTTP/S TCP Traffic:: + -You can send only HTTP and HTTPS traffic to applications in the migrated private space. Upgraded private spaces don't support non-HTTP/S TCP traffic. -+ -For in-place migrations with existing network connections (Transit Gateway or VPN), the CloudHub 2.0 private space infrastructure uses an internal IP range (`100.67.x.x`) that differs from the original VPC IP range. This IP range mismatch prevents TCP traffic that requires node-level access from reaching the private space through your on-premise network. -+ -To enable TCP traffic for migrated private spaces with network connections, add routes in your on-premise network to reach the private space infrastructure CIDR range, and coordinate with MuleSoft Support for required NAT configuration changes. -+ -If you can't add these routes, consider this limitation before starting the in-place migration. +Currently only HTTP and HTTPS traffic can be sent to applications in the migrated Private Space. TCP traffic is not supported at this time. == Understand Environment Association