PuppyIP Resource Center
Cloud Operations 5 min Published 2026-11-21

AWS Network Firewall NAT/Proxy Is GA: Egress Migration and Costs

AWS announced general availability of Network Firewall NAT/Proxy on November 19. One firewall policy can inspect explicit HTTP and HTTPS proxy traffic and traffic sent by VPC routes. Before migrating egress, check your Region, NAT Gateway reuse constraints, and both traffic paths.

AWS Network Firewall Explicit Proxy NAT Gateway VPC Egress

Service eligibility and regional restrictions

PuppyIP serves only compliant overseas businesses and their authorized personnel. Proxy services are not available in mainland China. The service may only be used for lawful business activities outside mainland China. Use of this service within mainland China is prohibited.

Hosting a proxy IP or server overseas does not change these restrictions. The service must not be provided to end users in mainland China through relaying, forwarding, sharing or resale. Before use, read the Terms of Service.

Key Takeaways

  • Applications send HTTP and HTTPS requests to the explicit proxy. VPC route tables send other traffic that requires routed inspection to firewall endpoints.
  • Network Firewall creates a NAT Gateway and firewall endpoint for each Availability Zone you add to a new NAT/Proxy firewall. You can also choose whether routed traffic uses NAT.
  • The November 19 notice lists 16 Regions, including Hong Kong, Tokyo, Singapore, and Frankfurt. Verify availability for your target Region.
  • Budget for firewall endpoint hours and traffic processing. The NAT Gateway discount depends on account, Region, network path, and matching usage.

Identify explicit proxy and VPC-routed traffic

With an explicit proxy, the application or client sends HTTP or HTTPS requests directly to the configured proxy listener. With routed inspection, the VPC route table sends traffic to the firewall endpoint. AWS's new mode lets both paths share one firewall policy.

To migrate one application first, check its proxy configuration and approved destinations, then test existing routed traffic independently. For workloads that require a fixed public source address, verify the egress IP from both paths.

Check the Region, VPC, and Availability Zones before creating a firewall

The November 19 announcement lists 16 Regions, including Northern Virginia, Oregon, Ireland, Frankfurt, Hong Kong, Tokyo, and Singapore. Verify the target Region in the announcement and identify the Availability Zones that need endpoints.

AWS documents a NAT Gateway and firewall endpoint in each Availability Zone you add to a new NAT/Proxy firewall. The primary endpoint must share a VPC with its gateway. Other VPCs can use associated endpoints in the firewall's deployed zones.

AWS says the new association requires a new firewall. You cannot attach an existing NAT Gateway in this setup. At creation, you can choose whether routed traffic also uses NAT. Record the old path and verify traffic, logs, and egress IPs on a test path before migrating.

Verify the TLS inspection scope for each path

AWS's new domain-based selective TLS inspection applies to explicit proxy traffic. If you plan to decrypt HTTPS, verify certificate trust on authorized test clients and check one controlled request that should be inspected and one that should pass without decryption.

For TLS inspection through an associated endpoint, AWS says the endpoint needs to be in the same account as the firewall. Verify the required features and policy scope before choosing a cross-account endpoint.

Pilot one application and define when to revert

Choose a low-risk application and two authorized test cases. One should be allowed and the other should be denied by the test policy. Match each result to its firewall log and check whether existing routed traffic was affected.

Record the previous proxy address or route configuration before switching. Restore the previous configuration if the application result, policy log, or source address observed by a partner differs from the expected result. Then investigate the affected traffic path.

Estimate firewall and NAT Gateway charges

For the target Region, estimate primary and secondary endpoint hours, gigabytes processed, and any Advanced Inspection and data transfer charges that apply. Identify the billable resources and egress path in your proposed design.

AWS's pricing page describes a discount for standard NAT Gateway hours and data processing matched to firewall usage in the same account, Region, and network path. Apply the terms to your selected architecture and usage. Include firewall, optional feature, and applicable data transfer charges.

Sources

Frequently Asked Questions

Can I turn an existing NAT Gateway into the firewall-managed gateway?

AWS says the new association cannot use an existing NAT Gateway and requires a new firewall. Validate a parallel path before switching workloads under your change plan.

Is the November 20 automated Internet firewall also generally available?

AWS announced it as a separate public preview. It enforces policies at internet gateways for the VPCs in scope. Check that preview's own Region and deployment terms.

How do I check which IP addresses my partner should allow after migration?

Send requests from a proxied application and an independent routed test to the same authorized test service. Record the public source IP observed by the receiver for each path and Availability Zone, then check the partner's allowlist.