AWS Network Firewall now supports native integration with AWS Transit Gateway for centralized traffic inspection in all AWS Regions where both services are available. This integration enables customers to directly attach a network firewall to a transit gateway and easily route traffic between these services for consistent traffic inspection. The new feature eliminates the need to manage dedicated VPC subnets and route tables when connecting these services.
You can use this capability to protect traffic across your entire AWS network including VPCs and on-premises networks connected via AWS Site-to-Site VPN or AWS Direct Connect. The integration improves network security and resiliency through automatic multi-AZ redundancy, ensuring continuous service availability across regions.
Native integration is available in all AWS Regions where both AWS Network Firewall and AWS Transit Gateway are supported.
To learn more, visit the AWS Network Firewall service documentation.
Categories:
Source: Amazon Web Services
Latest Posts
- Legacy SharePoint Online Content Delivery Network (CDN) domain to be retired—review configurations [MC1184996]
- Copilot can now automatically reschedule 1:1 meetings and personal events based on your preferences [MC1184999]
- Microsoft Teams: Improvements to “Activity in other accounts and orgs panel” [MC1184992]
- Migration of Name Pronunciation and Pronoun Controls to the People Settings Section in Org Settings [MC1184998]
This native integration between AWS Network Firewall and Transit Gateway is a big step forward for simplifying traffic inspection across regions. Eliminating the need for dedicated VPC subnets and route tables not only reduces complexity but also helps streamline network security architecture. Curious to see how this plays out in multi-account environments with centralized security operations.