November 20, 2026 · AWS
Amazon VPC IPAM policies now support automated internet firewall and AWS Lambda Web Functions and MicroVMs
Amazon Virtual Private Cloud (VPC) IP Address Manager (IPAM) policies now support AWS Network Firewall automated internet firewall and AWS Lambda Web Functions and MicroVMs. You can centrally configure IPAM policies across AWS accounts and AWS Regions to allocate public IPv4 addresses to these resources from specific IPAM pools, such as Bring Your Own IP (BYOIP) addresses or Amazon-provided contiguous IPv4 blocks. This enables a stronger security posture, simplifies network and security operations, and can reduce public IPv4 costs when you use BYOIP.
Many customers allowlist the public IPs of their AWS resources in network access control lists (ACLs) and firewalls. Previously, keeping these resources on allowlisted addresses depended on each application team. With this launch, you can define allocation rules for them alongside existing resource types, so security teams can add IP-based filters with confidence that these resources draw addresses from approved ranges. For Lambda Web Functions and MicroVMs, this covers the public IPv4 addresses used for outbound traffic through Lambda Network Connectors. If a pool runs out of addresses, resources fall back to Amazon-provided addresses. You can also share allocated ranges with partners through IPAM integration with AWS prefix lists.
The feature is available in all AWS commercial Regions, in both the Free Tier and Advanced Tier of VPC IPAM. To learn more, see the IPAM policies documentation page and the IPAM documentation. For pricing details, see the IPAM tab on the Amazon VPC Pricing page
Free. Unsubscribe any time.