AWS prescriptive-guidance documentation change
Summary
Updated terminology from 'AWS Direct Connect' to 'Direct Connect' in three table entries for consistency
Security assessment
The changes are purely terminological adjustments without altering technical meaning or security context. No security vulnerabilities or protections are mentioned or modified.
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 8c9227364..8bd7a0379 100644 --- a//prescriptive-guidance/latest/migration-f5-big-ip/interconnecting-vpcs.md +++ b//prescriptive-guidance/latest/migration-f5-big-ip/interconnecting-vpcs.md @@ -52,3 +52,3 @@ Client (sends SYN) | AWS Transit Gateway | VPC peering | VPN between VPCs | Solu -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). +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).