Networks & InfrastructureAws1 1 NatTransit GatewayCloud Wan
AWS Adds Native 1:1 NAT to Transit Gateway and Cloud WAN
AWS launched native 1:1 NAT for Transit Gateway and Cloud WAN plus free networking cost allocation for VPC, easing multi-cloud conflicts and per-app billing.
Networks & InfrastructureWhy it matters
- AWS introduced native 1:1 NAT for Transit Gateway and Cloud WAN, available in commercial Regions now
- The capability is IPv4-only and unsupported in appliance-mode VPC attachments
- FCA for Amazon VPC is free and does not change total AWS charges
- FCA excludes Bahrain, UAE, China and AWS GovCloud U.S. regions
- Pricing for the NAT feature follows existing Amazon VPC charges
The story
Amazon Web Services (AWS) has shipped native one-to-one network address translation (1:1 NAT) for AWS Transit Gateway and AWS Cloud WAN, removing a long-standing barrier in multi-cloud deployments, partner network integrations and post-merger network consolidation. The capability is available now in commercial AWS Regions that support the two services, with pricing governed by standard Amazon VPC charges.
The problem is well known to network engineers. When two networks use identical IPv4 address ranges, routing infrastructure cannot distinguish between the duplicate destination prefixes, and the networks simply stop communicating. The scenario arises most often after acquisitions, in partner interconnects and in multi-cloud architectures.
What does the new NAT capability change?
Previously, teams had two unattractive options: renumber entire networks, a disruptive and slow project, or deploy and operate separate NAT infrastructure themselves. The managed feature integrates with AWS Regional Private NAT Gateway and translates overlapping IPv4 ranges into unique prefixes without touching the underlying networks.
AWS demonstrated three deployment scenarios at launch:
- Connecting virtual private clouds (VPCs) with identical address ranges following an acquisition
- Resolving conflicts between AWS and another cloud provider, using AWS Interconnect – multicloud and Direct Connect gateway attachments
- Connecting external partner networks that advertise overlapping routes, via site-to-site VPN attachments on AWS Cloud WAN
Administrators configure translation rules at the network attachment level. Routing is then handled either automatically through AWS-generated system routes or through border gateway protocol (BGP) route advertisements.
There are constraints practitioners should note. The capability works with IPv4 only. It does not rewrite DNS responses, so AWS recommends updating DNS records to reflect translated addresses. Certain configurations, including VPC attachments running in appliance mode, are unsupported.
How does Flexible Cost Allocation work?
In a second launch, AWS introduced Networking Flexible Cost Allocation (FCA) for Amazon Virtual Private Cloud (VPC). The feature lets organizations attribute shared networking expenses to the applications and teams that actually generate the traffic, rather than spreading costs through workarounds.
The change addresses a real billing pain point. AWS Cost and Usage Reports previously consolidated networking usage into single line items, forcing customers to distribute expenses through custom scripts, VPC Flow Logs analysis or fixed-percentage splits. The new capability allocates usage automatically according to traffic sources.
FCA covers several cost categories:
- NAT gateway data processing and data transfer, including internet-bound traffic
- Data transfers involving Amazon Elastic Compute Cloud (EC2) instances within an AWS Region
- VPC peering connections
Activation requires two steps: attaching cost allocation policies to supported networking resources, and enabling split cost allocation data in the AWS Billing and Cost Management console.
The feature is free and does not change total AWS charges. It is available across AWS commercial Regions except Bahrain and the United Arab Emirates, and it is not offered in China Regions or AWS GovCloud U.S. regions.
What does this mean for network and cloud teams?
For enterprises mid-way through M&A integration or partner onboarding, the 1:1 NAT launch removes the need for a renumbering project or bespoke NAT middle layer, which typically consumed weeks of engineering time and added another failure point. The managed translation happens at attachment level, which keeps configuration close to existing Transit Gateway workflows.
For FinOps teams, FCA closes a visibility gap that made per-application chargeback approximate at best. Automatic attribution by traffic source replaces the fixed-percentage splits that often left business units disputing shared bills.
Both capabilities are available immediately in the Regions noted, and organizations running IPv4-heavy estates across multiple clouds can begin consolidating routing and refining chargeback without additional spend on the features themselves.
Also reported
Source: sdxcentral.com
More from Daniel Okafor
Show full bio
Senior reporter covering regulation, policy and their impact on Carrier business, 5G and 6G, fiber and broadband at Telecom Gazette.
559 articles