AWS Cloud WAN now supports BGP communities on Direct Connect attachments for routing policy

AWS Cloud WAN has introduced support for BGP communities on Direct Connect attachments, extending routing policy capabilities beyond Site-to-Site VPN and Connect attachments. Previously, BGP communities could only be evaluated on VPN and Connect links, limiting routing control for hybrid networks. The update allows enterprises to tag routes with routing intent on-premises and apply filtering or path preference rules within Cloud WAN. This change enables dynamic signaling of routing policies from on-premises environments over Direct Connect.

Customers can now use BGP communities to filter traffic between production and disaster recovery environments, prioritize preferred network paths, or restrict regional route propagation. The feature eliminates the need for manual policy replication or VPN overlay workarounds, reducing operational overhead. By propagating community tags back to on-premises routers, enterprises gain finer-grained control over hybrid network routing. This addresses long-standing limitations in managing complex hybrid architectures.

The new capability simplifies hybrid network orchestration by centralizing routing policy enforcement within AWS Cloud WAN. Enterprises no longer require separate configurations for VPN and Direct Connect attachments, streamlining network management. The feature also reduces the risk of misconfigurations that can arise from manual policy replication across environments. By consolidating routing controls, AWS aims to improve consistency and reliability in hybrid network deployments.

BGP community support on AWS Cloud WAN Direct Connect attachments is available in all AWS Regions where both AWS Direct Connect and AWS Cloud WAN are offered. Customers can reference the Cloud WAN Routing Policies documentation for the complete list of supported Regions. The feature is designed to enhance routing flexibility and operational efficiency for enterprise hybrid networks.