AWS Direct Connect introduces inbound prefix controls and higher prefix scale

AWS Direct Connect has introduced inbound prefix controls, enabling customers to manage and allocate inbound route-prefixes for private and transit virtual interfaces (VIFs) based on workload requirements. Previously limited to 100 prefixes per VIF, the new feature allows up to 1,000 IPv4 and IPv6 prefixes on dedicated and hosted connections. This eliminates the need for workarounds such as route summarization or segmenting networks across multiple VIFs or connections. The change simplifies network architecture by allowing direct route advertisements within the new capacity limits.

The feature introduces prefix capacity pools at the dedicated connection and Direct Connect gateway (DXGW) levels, enabling right-sized allocations per workload. For example, a transit VIF can be assigned a large prefix pool while a private VIF on the same connection receives a smaller allocation. Pool sizes scale with connection speed and link aggregation group (LAG) member counts, ensuring flexibility for varying network demands.

Customers can configure prefix allocations using the AWS Direct Connect console, CLI, or API. The new capability is available at no additional cost across all commercial AWS Regions, AWS GovCloud (US-East and US-West), and AWS China regions operated by Sinnet and NWCD. This expansion addresses the growing needs of enterprise networks requiring higher route capacity without architectural compromises.

To implement inbound prefix controls, users must allocate prefixes when creating or updating a VIF, drawing from the dedicated connection’s or DXGW’s pool. The feature supports both IPv4 and IPv6, with allocations managed per VIF type. For further details, AWS provides documentation in the AWS Direct Connect User Guide, outlining configuration steps and best practices for optimal use.