Release notes
Back to All

Nov 4, 2026 — NAT Gateways (BETA)

about 4 hours ago

The Beta release of NAT Gateways for Akamai Cloud Computing is now available.

NAT Gateways provide a managed, one-to-many Network Address Translation service that allows multiple Linodes within a VPC subnet to share public IPv4 addresses for outbound internet access while blocking unsolicited inbound connections.

Features

  • One-to-many NAT architecture: Share a single public IPv4 address across multiple Linodes by dividing available outbound ports into equal, isolated portset allocations.
  • Autoscaling mode (default): Automatically provisions public IPv4 addresses as workloads scale up and releases them when workloads scale down, supporting dynamic clusters without requiring static egress IPs.
  • Manual scaling mode: Assign reserved public IPv4 addresses to maintain fixed, known outbound IP addresses required for external firewall allowlists and third-party security rules.
  • Configurable portset sizes: Customize port allocations per Linode (default_ports_per_interface) from 64 ports up to 16,384 ports (default: 4,096 ports / up to 15 Linodes per IP) to tailor density to your workload's outbound connection needs. This Beta release supports portset sizes of 4096, (up to 15 nodes per IP), 8192 (up to 7 nodes per IP), and 16384 (up to 3 nodes per IP).
  • Seamless VPC subnet integration: Attach a NAT Gateway directly to a VPC subnet to route outbound traffic for all non-1:1 NAT interfaces. Service interfaces (such as NodeBalancer backends and DBaaS) automatically bypass the NAT Gateway.
📘

NAT Gateways Beta

NAT Gateways are currently in Beta. Please review the following operational constraints before deploying in production:

  • Autoscale IP Limit: Autoscaled NAT Gateways can provision up to 20 public IPv4 addresses by default. Higher limits may be approved on a case-by-case basis, subject to applicable conditions. Contact Customer Support to request a limit increase.
  • IAM permissions: Full NAT Gateway functionality is supported for unrestricted account users and IAM Service Accounts. However, restricted users may encounter limitations when creating, configuring, or viewing NAT Gateways.
  • High-Throughput & DDoS Protection: NAT Gateway Beta is designed for lower-throughput outbound traffic, such as API access and IP allowlisting. Traffic from a single public IP that exceeds monitored thresholds may trigger automated DDoS detection or mitigation safety measures. Customers with higher-throughput requirements should continue using 1:1 NAT during Beta.
  • Portset sizes: This Beta release supports portset sizes of 4096, (up to 15 nodes per IP), 8192 (up to 7 nodes per IP), and 16384 (up to 3 nodes per IP).
  • Terraform & CLI: Terraform and CLI support is not available during Beta. You can configure and manage NAT Gateways using Cloud Manager, and the Linode API.

New documentation pages

Learn more about NAT Gateway features, configuration workflows, and management procedures:

  • NAT Gateways Overview — An overview covering NAT Gateway features, portset allocations, allocation modes, and key differences between 1:1 NAT and NAT Gateways.
  • Getting started with NAT Gateways — Review prerequisites, interface requirements, and high-level deployment workflows.
  • Create a NAT Gateway — Step-by-step instructions for deploying a NAT Gateway and attaching it to a VPC subnet using Cloud Manager.
  • Managing NAT Gateways — Shows how to view gateway details, edit labels, manage reserved IPs in manual scaling mode, detach subnets, and delete gateways.

Updated documentation pages

The following pages were update to include NAT Gateway information:

API reference documentation

For new and updated API endpoints, see the Linode API reference for NAT Gateways.