Amazon Web Services (AWS) introduced new networking capabilities aimed at simplifying connectivity across complex cloud environments.
The first of the two launches saw AWS introduce native one-to-one network address translation (1:1 NAT) for AWS Transit Gateway and AWS Cloud WAN to resolve overlapping IP address conflicts that frequently complicate multi-cloud deployments, partner network integrations, and M&A activity. Such conflicts can prevent networks from communicating because routing infrastructure cannot distinguish between identical destination prefixes.
Where organizations traditionally addressed these conflicts by renumbering networks or deploying separate NAT infrastructure, the new capability integrates with AWS Regional Private NAT Gateway to translate overlapping IPv4 address ranges into unique prefixes without changing the underlying networks.
AWS demonstrated three deployment scenarios: connecting virtual private clouds (VPCs) with identical address ranges following an acquisition; resolving conflicts between AWS and another cloud provider through AWS Interconnect – multicloud and Direct Connect gateway attachments; and connecting external partner networks advertising overlapping routes through site-to-site VPN attachments on AWS Cloud WAN.
Administrators configure translation rules at the network attachment level, while routing can be managed automatically through AWS-generated system routes or through border gateway protocol (BGP) route advertisements.
AWS recommends that DNS records be updated to reflect translated addresses, as the service does not rewrite DNS responses. The capability is limited to IPv4, and certain configurations, including VPC attachments operating in appliance mode, are unsupported.
The managed 1:1 NAT capability is available in commercial AWS Regions supporting Transit Gateway and Cloud WAN, with pricing governed by Amazon VPC charges.
FCA for VCP on AWS
Separately, the hyperscaler introduced Networking Flexible Cost Allocation (FCA) for Amazon Virtual Private Cloud (VPC), which allows organizations to attribute shared networking expenses to the applications and teams responsible for generating them.
Previously, AWS Cost and Usage Reports consolidated networking usage into single line items, with customers distributing expenses through custom scripts, VPC Flow Logs analysis, or fixed-percentage splits. The new capability automatically allocates usage according to its traffic sources, helping organizations improve internal charging accuracy and track spending at the application level.
FCA covers NAT gateway data processing and data transfer, including internet-bound traffic, as well as data transfers involving Amazon Elastic Compute Cloud (EC2) instances within an AWS Region and VPC peering connections.
Users can activate the feature by attaching cost allocation policies to supported networking resources and enabling split cost allocation data in the AWS Billing and Cost Management console.
The feature, which is free and does not change total AWS charges, is available across AWS commercial Regions except Bahrain and the United Arab Emirates, as well as China Regions. It is not supported in AWS GovCloud U.S. regions.
Comments