Why and how to migrate to a Transit Gateway-attached AWS Network Firewall
Security Blog
This article explains how to migrate from traditional inspection VPC architectures to Transit Gateway-attached AWS Network Firewall, which simplifies network architecture and enables flexible cost allocation.
- Transit Gateway-attached Network Firewall eliminates need for dedicated inspection VPC
- Enables flexible cost allocation through Transit Gateway metering policies
- Reduces architectural complexity by removing inspection VPC management overhead
- Two common migration paths: separate inspection/egress VPCs or combined VPC
- Phased migration approach allows parallel testing before production cutover
- Preserve existing NAT gateway Elastic IPs during migration process
- Transit Gateway encryption not currently supported with native attachment
- Detailed migration guides available for Terraform, CloudFormation, and manual console steps
The migration uses a phased approach, testing with single spoke VPCs before migrating remaining traffic, minimizing downtime and risk.
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
Jun 16
2025
2025
AWS Network Firewall now supports AWS Transit Gateway native integration
Apr 26
2023
2023
Best practices and considerations to migrate from VPC Peering to AWS Transit Gateway
Apr 24
2026
2026
Introducing AWS Client VPN native AWS Transit Gateway attachment
Apr 24
2026
2026
AWS Client VPN now supports native AWS Transit Gateway integration
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.