✨ Add support for AWS Regional NAT Gateway #5791
Open
Add this suggestion to a batch that can be applied as a single commit. This suggestion is invalid because no changes were made to the code. Suggestions cannot be applied while the pull request is closed. Suggestions cannot be applied while viewing a subset of changes. Only one suggestion per line can be applied in a batch. Add this suggestion to a batch that can be applied as a single commit. Applying suggestions on deleted lines is not supported. You must change the existing code in this line in order to create a valid suggestion. Outdated suggestions cannot be applied. This suggestion has been applied or marked resolved. Suggestions cannot be applied from pending reviews. Suggestions cannot be applied on multi-line comments. Suggestions cannot be applied while the pull request is queued to merge. Suggestion cannot be applied right now. Please check back later.
What type of PR is this?
/kind feature
What this PR does / why we need it:
This PR implements support for AWS Regional NAT Gateways, a new feature announced by AWS in November 2025. Regional NAT Gateways provide automatic multi-AZ expansion with simplified network architecture and enhanced security compared to traditional zonal NAT Gateways.
Key Changes:
natGatewayAvailabilityModefield toVPCSpecwith enum validation (Zonal/Regional)reconcileRegionalNatGateway()for creating and managing a single NAT Gateway across all AZscreateRegionalNatGateway()usingVpcIdandAvailabilityModeparametersgetNatGatewayForSubnet()to support routing through regional NAT GatewaysBenefits:
Example Usage:
Which issue(s) this PR fixes:
Fixes #5790
Special notes for your reviewer:
AvailabilityModeandVpcIdparameters forCreateNatGatewayInputChecklist:
Release note: