Attachments - AWS Network Manager
Route evaluation

Attachments

You can work with core network attachments using the Amazon VPC Console or the command line or API.

Attachment states can be one of the following. Attachment states appear on the Attachments page of the AWS Cloud WAN console.

  • Creating — Creation of an attachment is in process.

  • Deleting — Deletion of an attachment is in process.

  • Pending network update — Waiting for the connection of attachments to the core network.

  • Pending tag acceptance — Waiting for the core network owner to review the tag change for an attachment.

  • Pending attachment acceptance — Waiting for the core network owner to accept or reject an attachment.

  • Rejected — The core network owner rejected the attachment.

  • Available — The attachment is fully functional.

  • Failed — The attachment failed to attach to the core network. For example, this might be due to an input error or a service linked role issue.

The following are the supported core network attachment types.

  • Connect

    You can also create a Connect peer through the Network Manager console.

  • VPC

  • Site-toSite VPN

  • Transit gateway route table

You can create an attachment using either using the Network Manager console or by using the command line or API.

Route evaluation

Cloud WAN evaluates routes in the following order:

  1. The most specific route for the destination

  2. For routes with the same destination IP address, but different targets, the following route priority is used:

    1. Static routes

    2. VPC-propagated routes in the same Region.

    3. For dynamic routes received at the core network with an unequal AS path length and/or MED BGP attributes, Cloud WAN evaluates them in the following order:

      1. AS path length

      2. MED

    4. For dynamic routes received at the core network with equal AS path length and MED BGP attributes, Cloud WAN evaluates them in the following order:

      1. Cloud WAN Connect-propagates routes in the same Region.

      2. Site-to-Site VPN-propagated routes in the same Region.

      3. Routes propagated from other sources, such as transit gateway peering (which also includes AWS Direct Connect gateway-propagated routes) and core network edges in other remote Regions over the AWS global infrastructure. If identical routes are received from two or more sources, a single attachment will be chosen in a deterministically random manner.

Topics