AWS prescriptive-guidance documentation change
Summary
Changed 'AWS Direct Connect gateway' to 'Direct Connect gateway' for terminology consistency
Security assessment
This is a minor terminology adjustment without security implications. The change aligns with product naming conventions but doesn't modify security controls or introduce new security-related content about the traffic inspection solution.
Diff
diff --git a/prescriptive-guidance/latest/inline-traffic-inspection-third-party-appliances/solution-options.md b/prescriptive-guidance/latest/inline-traffic-inspection-third-party-appliances/solution-options.md index 628d0f4c4..cd9063712 100644 --- a//prescriptive-guidance/latest/inline-traffic-inspection-third-party-appliances/solution-options.md +++ b//prescriptive-guidance/latest/inline-traffic-inspection-third-party-appliances/solution-options.md @@ -30 +30 @@ The following resources are used in the three options for this solution: - * A transit gateway to interconnect the VPCs, in addition to providing on-premises connectivity through the Transit Gateway virtual interface and AWS Direct Connect gateway or with a VPN attachment for AWS Site-to-Site VPN. + * A transit gateway to interconnect the VPCs, in addition to providing on-premises connectivity through the Transit Gateway virtual interface and Direct Connect gateway or with a VPN attachment for AWS Site-to-Site VPN.