As an Amazon Associate I earn from qualifying purchases from

Cisco SD-WAN: Driving Community Effectivity and Accelerating Cloud Integration with AWS Cloud WAN

Contributing creator:
Vipul Shah, Engineering Product Supervisor – Cisco SD WAN

In as we speak’s world, enterprise prospects are dominantly centered on their customers and purposes. The bridge that stitches them collectively is the Enterprise WAN, which not solely must align with the rising advanced wants of its customers but in addition must be safe, scalable, resilient, and programable. Cisco SD-WAN brings collectively customers, branches, purposes, and knowledge facilities (on-prem or cloud) below one cohesive structure to satisfy as we speak’s expectations. Cisco vManage offers a single pane of glass to provision, function, and handle this community.

The enterprise cloud footprint is rising at a fast tempo, leading to advanced insurance policies and designs for connectivity throughout enterprise websites and workloads within the cloud. Conventional AWS cloud-native service like AWS Transit Gateway is a regional assemble, which performs nicely in a design involving transit gateway peering throughout a small variety of AWS Areas. As extra Areas are added, the community can get exponentially advanced with extra transit gateway peering. Additionally, separate route tables for segmentation add one other layer of complexity to the community.

Contributing creator:
Marty Ma, Technical Advertising Lead – Cisco SD-WAN

Questions we usually hear from our prospects are:

  1. How do I simply deploy and handle a cloud community for segmented customers, purposes, and different sources dispersed throughout areas, whereas sustaining a hardened safety posture?
  2. Can my community be agile sufficient to rapidly adapt to altering insurance policies and software necessities?
  3. What’s the affect on the person expertise for a multi-region software?
  4. My customers related to area X are having inconsistent experiences accessing an software in area Y. What can I do?
  5. Can I exploit the Cloud Service Supplier (CSP) spine as a quicker strategy to join my websites as an alternative of much less dependable web?

It mainly drills all the way down to having a extra sturdy means to attach site-to-site, site-to-cloud workloads, and inter-Area workloads in AWS. That is precisely what the Cisco SD-WAN and AWS Cloud WAN integration can provide.


AWS Cloud WAN is a managed WAN answer that was introduced at AWS re:Invent 2021. It permits customers to construct a multi-Area world WAN community on the AWS spine utilizing easy coverage statements. It removes the necessity to sew collectively a number of Areas as is the case with AWS Transit Gateway.


The important thing constructing blocks of the AWS Cloud WAN structure are:

  • Cloud WAN: Cloud WAN is a managed WAN service that permits enterprises to determine community connectivity throughout the Area utilizing the AWS spine. Cloud WAN will be enabled in a Area that’s close to to websites, customers, or workloads. Cloud WAN contains CNE (Core Community Edge) which is a Regional Connection Level. Sources are related to CNE utilizing attachments like VPC, VPN, and so on.
  • Core Community Coverage (CNP): A single JSON coverage doc that defines the entire configuration of the Cloud WAN. It lists the Areas via which the Cloud WAN extends. It carries the phase info which is used for routing separation. It additionally defines how the VPC and VPN attachments are related to the community segments, together with route leak configuration for shared companies use-cases.
  • Attachments: Attachments are a strategy to join sources to the Cloud WAN. The sorts of attachments are VPC, VPN, Join, and TGW.
  • Core Community Edge (CNE): The regional connection level managed by AWS in every Area, as outlined within the Core Community Coverage. Each attachment connects to a Core Community Edge.

Based mostly on CNP configuration, AWS Cloud WAN will create CNE within the configured Areas. The CNEs throughout all of the Areas will mechanically peer with one another. Cloud WAN additionally carries phase info throughout the Area, thus mechanically creating end-to-end routing area for every particular person phase. Sources are connected to the CNE and are mapped to a phase.

This Cloud WAN structure’s built-in automation manages the complexity and offers prospects with a easy plug-n-play method to deploy and handle the cloud community.

Cisco SD-WAN Integration

The Cisco SD-WAN Cloud OnRamp for Multicloud with AWS, offers enterprise prospects the next capabilities to deploy a safe SD-WAN material over a dependable AWS Cloud WAN spine.

  1. Automation: The built-in answer provides customers the automation to combine their SD-WAN insurance policies with AWS cloud-native constructs for dependable and constant websites and cloud deployments. Cisco vManage simplifies the method of making and managing the Core Community Coverage (CNP) doc and AWS manages the implementation particulars.
  2. Safety: AWS Cloud WAN’s built-in community segmentation permits seamless integration with Cisco SD-WAN to supply end-to-end segmentation. Utilizing a easy workflow in Cisco vManage, enterprise prospects can deploy provider grade transport (throughout Areas) utilizing the AWS spine.
  3. Observability: Cisco SD-WAN integration with AWS Cloud WAN simplifies operations by enabling visibility for the SD-WAN overlay and AWS Cloud WAN underlay within the vManage portal.

Cisco vManage will:

  • Uncover workload VPC throughout areas
  • Tag the VPC attachment to map to a desired phase (VPN)
  • Deploy Cloud Gateway (CGW)
  • Instantiate CNE within the required area
  • Instantiate Transit VPC (TVPC) with pair of Cisco SD-WAN digital edge routers
  • Set up VPN or Join attachment and BGP peering between CNE and SD-WAN digital edge router for every phase/VPN
  • Understand Intent by mapping SD-WAN VPN to AWS Cloud WAN segments

With the assistance of Cloud Gateway (CGW), the Cisco SD-WAN material is prolonged to the sting of the AWS Cloud within the desired Area. As proven within the topology above, Cisco vManage manages the SD-WAN coverage throughout the material. This allows vManage to push constant SD-WAN insurance policies to the branches and Cisco SD-WAN digital edge router within the TVPC. With the AWS Cloud WAN integration, vManage can create and replace the CNP doc. Utilizing API calls, vManage pushes the CNP to AWS. AWS Cloud WAN then updates obligatory configuration primarily based on the insurance policies outlined within the CNP paperwork. Thus, Cisco SD-WAN intuitively helps create and handle end-to-end segments from the customers to the appliance.

Automation Workflow

Cloud OnRamp for Multicloud automation follows a easy 4 step workflow. Customers can observe these easy steps to implement AWS Cloud WAN integration:

1. Setup

Buyer selects the answer and defines world parameters for the AWS Cloud WAN integration.

Cisco vManage OnRamp for Multicloud configuration

2. Uncover

Buyer makes use of the Uncover possibility to find host VPCs (workload VPCs) within the cloud. These VPCs can now be tagged with the phase identify which attaches them to the specified VPN.

3. Deploy

At this step we deploy CGW within the AWS Area. Repeat this step for all of the required AWS Areas to construct a multi-region AWS Cloud WAN community.

4. Declare Intent

As a remaining step, customers can map SD-WAN VPNs to AWS Cloud WAN segments by merely clicking on the precise matrix to determine the supposed connections. Within the instance under, VPN 61 is mapped to SALES phase. VPN2 and VPN10 are being configured to map to TEST and PROD segments respectively.

That’s all it takes to carry up the AWS Cloud WAN integration utilizing vManage. 😊

The complimenting partnership between Cisco and AWS delivers a simplified WAN for:

  • Unified Administration – leverage an intuitive workflow to deploy site-to-cloud and site-to-site connectivity over a dependable spine community, with end-to-end visibility and assurance, by way of single UI, Cisco vManage.
  • Safety – The built-in segmentation in AWS Cloud WAN not solely simplifies VPN mapping with Cisco SD-WAN but in addition permits propagation of unified business-intent insurance policies throughout the community.
  • Diminished TCO – Scale back deployment time for overlay and underlays, capacity to dynamically deploy in software program is important as conventional MPLS circuits takes weeks or months to provision. Considerably decrease OpEx via improved efficiency and a dependable, on-demand consumption mannequin provisioned via Cisco vManage.

To summarize, Cisco SD-WAN and AWS Cloud WAN integration will simplify Website-to-Cloud, Website-to-Website, and inter-region workload use-cases for the shoppers. This alleviates prospects from coping with the complexity of as we speak’s WAN requirement and focuses on their customers, purposes, and core enterprise.

To study extra:


We will be happy to hear your thoughts

Leave a reply

Enable registration in settings - general
Compare items
  • Total (0)
Shopping cart