Best Practices from Fortinet for Troubleshooting Common Issues with Gateway Load Balancer
AWS Partner Network Blog
The article provides best practices from Fortinet for troubleshooting common issues with the AWS Gateway Load Balancer (GWLB) when integrating Fortinet's FortiGate Next-Generation Firewall (NGFW) appliances.
Specifically, the article covers:
- Troubleshooting issues with GWLB health checks not working properly with third-party appliances
- Identifying routing issues that prevent packets from reaching third-party appliances
- Troubleshooting when packets reach the appliance but don't get back to the destination via GWLB
- Addressing application session timeouts after migration to GWLB
- Resolving issues with source Availability Zone not being preserved when GWLB receives traffic from AWS Transit Gateway
- Conclusion summarizing key points for troubleshooting GWLB deployments with third-party appliances
The AWS News Feed is currently looking for gold sponsors. If you want to support the AWS community and reach a large audience of AWS professionals, consider sponsoring the AWS News Feed.
Related articles
Oct 25
2024
2024
Simplify firewall deployments using centralized inspection architecture with Gateway Load Balancer
Jan 27
2025
2025
Load Balancer Migration to AWS: Recommended Strategies and Best Practices
Sep 3
2024
2024
Introducing configurable TCP idle timeout for Gateway Load Balancer
Mar 31
2026
2026
Streamline your Amazon EKS deployments with Gateway API support for AWS Load Balancer Controller and Amazon VPC Lattice
The AWS News Feed is currently looking for silver sponsors. If you want to support the AWS community and reach a large audience of AWS professionals, consider sponsoring the AWS News Feed.