AWS prescriptive-guidance documentation change
Summary
Fixed a URL formatting issue by adding an extra slash in the documentation link
Security assessment
The change only corrects a hyperlink URL syntax without altering security-related content. No security implications exist as it doesn't address vulnerabilities or modify security guidance.
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 5b630ee43..eb3862cc9 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 @@ -32 +32 @@ 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.