AWS prescriptive-guidance documentation change
Summary
Updated navigation link, image path, apostrophe formatting, and documentation URL
Security assessment
Changes are cosmetic (apostrophe correction) and maintenance-related (image path update, URL fix). The existing security discussion about asymmetric routing remains unchanged with no new security guidance added.
Diff
diff --git a/prescriptive-guidance/latest/inline-traffic-inspection-third-party-appliances/transit-gateway-asymmetric-routing.md b/prescriptive-guidance/latest/inline-traffic-inspection-third-party-appliances/transit-gateway-asymmetric-routing.md index 24046ed37..0c8be0776 100644 --- a//prescriptive-guidance/latest/inline-traffic-inspection-third-party-appliances/transit-gateway-asymmetric-routing.md +++ b//prescriptive-guidance/latest/inline-traffic-inspection-third-party-appliances/transit-gateway-asymmetric-routing.md @@ -5 +5 @@ -[Documentation](/index.html)[AWS Prescriptive Guidance](https://aws.amazon.com/prescriptive-guidance/)[Implementing inline traffic inspection using third-party security appliances](welcome.html) +[Documentation](/index.html)[AWS Prescriptive Guidance](https://aws.amazon.com/prescriptive-guidance/)[Implementing inline traffic inspection using third-party security appliances](introduction.html) @@ -9 +9 @@ -Before describing the different traffic inspection use cases, it’s important to understand how traffic flows through AWS Transit Gateway. The following diagram shows the flow of traffic through Transit Gateway. +Before describing the different traffic inspection use cases, it's important to understand how traffic flows through AWS Transit Gateway. The following diagram shows the flow of traffic through Transit Gateway. @@ -11 +11 @@ Before describing the different traffic inspection use cases, it’s important t - + @@ -34 +34 @@ The diagram shows the traffic flow when a source Amazon Elastic Compute Cloud (A -By default, Transit Gateway maintains Availability Zone affinity, which means that it uses the same Availability Zone to forward the traffic from where it entered the transit gateway. Although this is appropriate for most use cases, this approach can cause asymmetric routing issues for stateful firewall appliances. Asymmetric routing occurs when the request and response use different network interfaces, which can cause traffic to be dropped. To avoid this, you should turn on appliance mode in the appliance VPC’s transit gateway attachment. This resolves asymmetric routing issues in VPC-to-VPC architecture patterns when the source and destination EC2 instances are in two different Availability Zones and across different VPCs. For more information about this, see [Appliance in a shared services VPC](https://docs.aws.amazon.com//vpc/latest/tgw/transit-gateway-appliance-scenario.html) in the Amazon Virtual Private Cloud (Amazon VPC) documentation. +By default, Transit Gateway maintains Availability Zone affinity, which means that it uses the same Availability Zone to forward the traffic from where it entered the transit gateway. Although this is appropriate for most use cases, this approach can cause asymmetric routing issues for stateful firewall appliances. Asymmetric routing occurs when the request and response use different network interfaces, which can cause traffic to be dropped. To avoid this, you should turn on appliance mode in the appliance VPC's transit gateway attachment. This resolves asymmetric routing issues in VPC-to-VPC architecture patterns when the source and destination EC2 instances are in two different Availability Zones and across different VPCs. For more information about this, see [Appliance in a shared services VPC](https://docs.aws.amazon.com/vpc/latest/tgw/transit-gateway-appliance-scenario.html) in the Amazon Virtual Private Cloud (Amazon VPC) documentation.