AWS Transit Gateway now supports managed 1:1 NAT for overlapping networks. What does that simplify, and how does the Regional Private NAT Gateway fit in?
How does the new Transit Gateway 1:1 NAT help with overlapping networks?
Answers
It lets you connect private networks that use the same IP ranges without renumbering either side. The managed translation handles source and destination NAT on the attachments, so you don't need to deploy a NAT appliance or write return-traffic rules for that setup.
AWS Cloud WAN supports the same attachment-level feature too.
Reply to this answer
The Regional Private NAT Gateway detail is a little confusing. AWS describes the feature as using one, but the source discussion notes that customers could not create Regional Private NAT Gateways directly at the time. That doesn't necessarily mean you need to create one yourself to use the managed integration.
Reply to this answer
The practical win is less NAT plumbing for overlapping CIDRs. NAT instances were an option before, but they left you managing the instances and the translation setup. This moves that work into a managed feature.
Reply to this answer
Add your answer
Answers are reviewed before publication.
p.693!gobletnotch:
Worth checking the current Transit Gateway documentation for the setup steps and availability, rather than assuming the standalone NAT gateway options are identical.