#NETWORK CONNECT SERVICE SOFTWARE#
#NETWORK CONNECT SERVICE SERIES#

This can be seen in Figure 7.ДЇigure 7 вЂ“ Pending Acceptance of the peering requestДЇrom this point, weвЂ™ll transition to the AWS console for the account ID that we are peering with to complete the peering request. This indicates the associated must be accepted in the AWS Console of the target AWS account ID. If you click on the account thatвЂ™s being added you can see that the peering is in a PENDING ACCEPTANCE status. In the VMC console, the External TGW status will show as IN PROGRESS as shown in Figure 6.ДЇigure 6 вЂ“ External TGW Peering In Progress

#NETWORK CONNECT SERVICE SERIES#

This is an asynchronous series of API calls that may take up to 10 minutes to complete. Once the Add button is clicked, the process to establish a peering relationship between the VTGW and the AWS TGW begins.

Routes: AWS resource destination prefixes reachable via this peering connection.

VMC on AWS Region: Region where the VTGW resides.

TGW Location: Region where the TGW being peered with resides.TGW ID: ID of the AWS TGW being peered with.AWS Account ID: ID of the AWS Account where the TGW being peered with resides.Fill in the appropriate fields as described below. When the Add TGW button is clicked the dialog in Figure 5 appears. Once there, weвЂ™ll go to the External TGW tab and click on add TGW as shown below in Figure 4. In our topology, the group is called TPM-VTGW. To begin building this topology, weвЂ™ll start in the VMC Console and go to the SDDC Groups tab where weвЂ™ll navigate to the SDDC Group we want to configure the intra-region peering session in. The topology in Figure 3 will be built throughout the remainder of this article.ДЇigure 3 вЂ“ Intra-Region VTGW to TGW Peering Topology for Lab Now that weвЂ™ve established the primary use case, we can focus on a specific topology and review the configuration steps. The elimination of additional connectivity points simplifies the design by reducing the number of hops, route tables that would need management and reduces attachments. With the intra-region peering option, topologies can transition from the one depicted in Figure 1 to the topology illustrated in Figure 2.ДЇigure 1 вЂ“ Transit VPC Architecture for Intra-Region ConnectivityДЇigure 2 вЂ“ Intra-Region VTGW to TGW Peering While this works, there is additional protocol and management overhead with either approach and potential bandwidth bottlenecks. Prior to the intra-region peering feature customers would have to either use IPSec VPNs or Transit VPC architectures to provide the connectivity they required. ItвЂ™s not uncommon for our customers to have a footprint of native AWS services in a region that use AWS TGW connectivity in addition to a VMware Cloud on AWS SDDC footprint. Before we get into the configuration, letвЂ™s review the primary use case for this solution. This article will delve into one of the use cases and the details of the configuration for this feature.

To get access to this feature, please reach out to your VMware account team. Equally exciting is that this feature will be available to VMware Cloud on AWS customers with SDDCs that are on any version. VMware and AWS have been working on this solution diligently and we are excited to announce VMware Cloud on AWS support for this new capability in this announcement blog. However, there has been one gap in the connectivity вЂ“ the ability to peer the VMware Managed Transit Gateway (VTGW) with a native AWS Transit Gateway (TGW).ДЄt AWS re:Invent 2021, the ability to peer VTGWs to AWS TGWs in the same region, also referred to as intra-region peering was announced. These capabilities combine to provide a comprehensive networking solution to address some of the most challenging networking requirements. Since the initial offering in 2020 we have worked with our partner, AWS, to expand the serviceвЂ™s capabilities to include SDDC Grouping across multiple regions in addition to support for Transit/Security VPC models.

There are hundreds of customers using this feature across the fleet in a myriad of combinations.

#NETWORK CONNECT SERVICE SOFTWARE#

VMware Transit Connect has proven itself as a valuable tool to enable high bandwidth and speed connectivity for VMware Cloud on AWS customers and their Software Defined Data Centers (SDDCs).

Network connect service