AWS prescriptive-guidance documentation change
Summary
Updated breadcrumb navigation link and standardized 'AWS Direct Connect' naming in VPC connectivity scenarios
Security assessment
Changes are limited to navigation links and service name branding (adding 'AWS' prefix). Technical content about routing, bandwidth limits, and SNAT behavior remains unchanged with no security implications. No vulnerabilities or security features are introduced or discussed.
Diff
diff --git a/prescriptive-guidance/latest/migration-f5-big-ip/interconnecting-vpcs.md b/prescriptive-guidance/latest/migration-f5-big-ip/interconnecting-vpcs.md index 4d0ed8bd3..b0ad3e01f 100644 --- a//prescriptive-guidance/latest/migration-f5-big-ip/interconnecting-vpcs.md +++ b//prescriptive-guidance/latest/migration-f5-big-ip/interconnecting-vpcs.md @@ -5 +5 @@ -[Documentation](/index.html)[AWS Prescriptive Guidance](https://aws.amazon.com/prescriptive-guidance/)[Migrating from F5 BIG-IP to F5 BIG-IP VE on the AWS Cloud](welcome.html) +[Documentation](/index.html)[AWS Prescriptive Guidance](https://aws.amazon.com/prescriptive-guidance/)[Migrating from F5 BIG-IP to F5 BIG-IP VE on the AWS Cloud](introduction.html) @@ -54,3 +54,3 @@ Client (sends SYN) | AWS Transit Gateway | VPC peering | VPN between VPCs | Solu -Internet or Direct Connect to service in a single VPC with a public or private subnet. | N/A | N/A | N/A | Traffic traverses internet gateway, or virtual gateway - does not need to cross more than the VPC boundary. VPC acts as designed stub networks. Traffic ingresses from on premises to the AWS Cloud (Direct Connect, VPN). -Internet or Direct Connect in a VPC with clients in other VPCs (for example, pool members in another VPC), no SNAT. | Yes | No | Yes | AWS Transit Gateway or VPNs allow the traffic to bypass the VPC peering filter that only VPC-assigned CIDRs can pass. VPN solutions will be constrained. No equal-cost multi-path routing (ECMP) (only a single route) and no bandwidth (about 1.2 GB-seconds per tunnel, in general only one tunnel). -Internet or Direct Connect to a service in a VPC with customers in other VPCs (for example, pool members in another VPC), with SNAT. | Yes (but not required) | Yes | Yes (but not required) | Since the interconnection between the VPCs sees traffic from VPC-assigned CIDRs, any will work. VPN solutions will be constrained. No ECMP (only a single route) and no bandwidth (about 1.2 GB-seconds per tunnel, in general only one tunnel). +Internet or AWS Direct Connect to service in a single VPC with a public or private subnet.| N/A| N/A| N/A| Traffic traverses internet gateway, or virtual gateway - does not need to cross more than the VPC boundary. VPC acts as designed stub networks. Traffic ingresses from on premises to the AWS Cloud (AWS Direct Connect, VPN). +Internet or AWS Direct Connect in a VPC with clients in other VPCs (for example, pool members in another VPC), no SNAT.| Yes| No| Yes| AWS Transit Gateway or VPNs allow the traffic to bypass the VPC peering filter that only VPC-assigned CIDRs can pass.VPN solutions will be constrained. No equal-cost multi-path routing (ECMP) (only a single route) and no bandwidth (about 1.2 GB-seconds per tunnel, in general only one tunnel). +Internet or AWS Direct Connect to a service in a VPC with customers in other VPCs (for example, pool members in another VPC), with SNAT.| Yes (but not required)| Yes| Yes (but not required)| Since the interconnection between the VPCs sees traffic from VPC-assigned CIDRs, any will work.VPN solutions will be constrained. No ECMP (only a single route) and no bandwidth (about 1.2 GB-seconds per tunnel, in general only one tunnel).