Rapid News Brief

AWS introduced automated Internet firewall in public preview Nov. 20, bringing centralized Network Firewall policies to the internet gateways of selected Virtual Private Clouds. The mode includes native network address translation. AWS says teams can deploy it without changing routing inside each VPC and extend their policies to future VPCs and subnets. The preview excludes AWS GovCloud and China Regions.

Monitoring is not blocking

The setup guide defaults to Monitor mode, which logs matching traffic without blocking it. Enforce mode blocks traffic matching a blocking rule. Coverage is also scoped: administrators can exclude subnets, and unsupported Availability Zones are not inspected. Traffic using VPC gateway endpoints does not pass through the internet gateway and is outside that inspection path.

Other preview limits include no Regional NAT or NAT64 support, and exclusions for EC2 Mac and specified machine-learning instance types. Those limits mean the new mode should not be read as protection for every cloud resource. Its relevant boundary is traffic through the internet gateways covered by the deployment.

For infrastructure teams, that makes mode and scope separate rollout questions. A policy can produce useful observations without stopping a connection. Reviewing the intended paths and excluded workloads is therefore part of interpreting what a deployment actually covers, not an optional follow-up to the announcement.

Separate the two releases

AWS’s Nov. 19 technical blog describes a different Network Firewall update: general availability of its explicit proxy, alongside native NAT integration for routed firewalls. That setup can combine HTTP and HTTPS proxying with routed firewall functions. Applications using the explicit proxy are configured to send requests to its hostname; other traffic is routed to a firewall endpoint.

The blog describes centralized egress for networks with overlapping address ranges, using a NAT Gateway managed by Network Firewall. It is related infrastructure, not evidence that the next day’s internet-gateway preview is generally available. Operators evaluating the announcements need to distinguish the deployment model and release status before treating either one as a change to their existing protection.