PuppyIP Resource Center
Cloud Operations 6 min Published 2026-11-14

AWS Cloud WAN Direct Connect BGP Communities: What Is Preserved and What to Check

On November 12, 2026, AWS added support for standard BGP communities on Cloud WAN Direct Connect attachments. Only the communities on Direct Connect’s selected best path for each prefix reach the core network; large, extended, and communities with several AWS-reserved first ASNs are removed. Check the Transit VIF and gateway/core-network/segment relationship, then review policy order before diagnosing a missing community.

AWS Cloud WAN AWS Direct Connect BGP communities Hybrid cloud routing

Service eligibility and regional restrictions

PuppyIP serves only compliant overseas businesses and their authorized personnel. Proxy services are not available in mainland China. The service may only be used for lawful business activities outside mainland China. Use of this service within mainland China is prohibited.

Hosting a proxy IP or server overseas does not change these restrictions. The service must not be provided to end users in mainland China through relaying, forwarding, sharing or resale. Before use, read the Terms of Service.

Key Takeaways

  • The feature applies to Direct Connect attachments only in Regions where both AWS Cloud WAN and Direct Connect are available; the announcement does not specify fees.
  • Standard communities advertised over a Transit VIF can be preserved through the Direct Connect gateway, but only on the selected best path for each prefix.
  • Large and extended communities, plus communities whose first ASN is 7224, 10124, 17493, 9059, or 4001, are removed before reaching the core network. Use your own ASN outside the core network ASN range.
  • Cloud WAN allow/drop actions are terminal, unmatched routes are allowed by default, and summarization resets community attributes. The route-information API is pre-policy.

What launched, and where is it available?

On November 12, 2026, AWS announced that Cloud WAN Routing Policy now supports BGP communities on Direct Connect attachments. Cloud WAN routing policies already supported Site-to-Site VPN and Connect attachments. With Direct Connect, an on-premises router can tag route intent, then Cloud WAN policies can match communities, filter routes, or change path preferences.

The feature is available only in Regions where both AWS Cloud WAN and AWS Direct Connect are available. The announcement does not state a price, so this article does not call the feature free. It also does not promise a particular performance, latency, or availability outcome.

Confirm the Direct Connect attachment prerequisites

The association requires an existing Direct Connect gateway and a Cloud WAN core network. Cloud WAN uses a transit virtual interface (Transit VIF) for connectivity. A Direct Connect gateway can be associated with one core network and one segment in that network. Its ASN must be outside the ASN range configured for the core network.

This Cloud WAN attachment does not support allowed-prefix lists. All prefixes in the associated segment are advertised to the Direct Connect gateway. An allowed-prefix list is different from a Cloud WAN routing policy filter: policies can match prefixes, prefix lists, or communities, but that does not make the association-level allowed-prefix list available.

What a BGP community means, and why some tags disappear

A BGP community is a standard label attached to a route to express routing intent. A standard community is written as ASN:value, such as the hypothetical 65001:200; use that value only if it meets your actual ASN and core-network range restrictions. The label is not the destination prefix itself; a Cloud WAN policy can match it to filter a route or influence path preference. Standard communities advertised over a Transit VIF are preserved through the Direct Connect gateway to the Cloud WAN core network.

Direct Connect chooses one best path for each prefix first. If several locations advertise the same prefix with different communities, only the communities on the selected best path are preserved. Large BGP communities (RFC 8092), extended communities such as route targets, and communities whose first ASN is 7224, 10124, 17493, 9059, or 4001 are removed before the route reaches the core network. Use your own ASN first, outside the core network ASN range.

How policies allow, drop, or summarize routes

A routing policy can match prefixes, prefix lists, or BGP communities and filter routes, set path preferences, or add and remove communities. Allow and drop are terminal actions: after a route matches either one, no later rules are evaluated. A route that reaches the end without matching a terminal action is allowed, with any non-terminal modifications already applied.

Route summarization removes the matched specific prefixes and replaces them with a summary prefix. The summary is a new route with reset attributes, including an empty community list. Support also depends on attachment type: Transit Gateway route table attachments do not support BGP communities, while VPC attachments support only inbound allow/drop route filtering from the VPC to the core network.

Do not treat pre-policy information as the final result

When investigating missing communities, separate Direct Connect best-path selection and community restrictions from Cloud WAN policy matching and terminal actions. list-core-network-routing-information is an API name; it shows routing information before policies are applied, so it cannot by itself prove that a route was finally allowed or advertised.

An authorized network administrator can first confirm the Region, Transit VIF, gateway/core-network/segment association, first ASN in each community, and rule order, then verify the expected route at the peer using the team’s existing operations process. The sources do not require automatic removal of existing VPN paths. Do not treat the feature as a guarantee that a VPN can be safely replaced automatically. This article summarizes the official documentation; no configuration was run or verified.

Sources

Frequently Asked Questions

Does sharing a segment across Regions automatically extend the Direct Connect attachment to all of them?

Not necessarily. When creating the association, you can select all core network edge locations in the segment or choose individual locations. Check the locations actually selected for the attachment; segment sharing alone does not establish that the association covers another Region.

Can I modify the Cloud WAN association through the Direct Connect console or API?

Manage this association through the Cloud WAN console, APIs, or command line. The Direct Connect console, APIs, and CLI reflect the association and can verify that it was created, but cannot modify it.