( upbeat music) – Hi, I’m Simon, a Cloud Support Engineer here at the AWS office in Cape Town. Sometimes clients ask me how they can migratetheir site-to-site VPN from a virtual privategateway to a transit gateway. I said about the transit gatewayallows you to attach VPCs, direct connect gateways, andVPNs for interconnectivity. I’ll evidence you how you can modify your existing site-to-site VPN’s target from a virtual gatewayto a transit gateway.Let’s get started. After logging into theAWS Management Console, navigate to VPC Console. In the navigation board on the left, go to Transit Gateway, choose Create Transit Gateway. From here you can giveyour Transit Gateway a mention and description. I’ll honour excavation TGW-1. If you plan on migrating a dynamic VPN, there is a requirement add your BGP ASN number here. Keep this the same as your previous site-to-site VPN AS figure, so that you are eligible to eschewed reconfiguringyour client gateway. Make sure you enabled Autoaccept shared attachments to enable automated acceptanceof cross chronicle components. Choose Create TransitGateway and sounds Close. Now we need to attach your newly created transitgateway to your VPC. Go to Transit Gateway Attachmentsin the piloting body, and then select CreateTransit Gateway Attachment. From the drop down menufor Transit Gateway ID, you can select your recentlycreated transit gateway.Set your affection type as VPC, and add a list tagfor your component, I’ll name mine VPC-1-Attachment. From the VPC ID drop down you can select the VPC you want to attachto the transit gateway, and then select the subnets you want the transportation gateway ENIs to reside. Choose Create Attachment and then Close. You’ve now successfullycreated your transit gateway, and fixed it to your VPC. And now to migrate yourexisting site-to-site VPN away from the virtual private gateway to your brand-new transport gateway. If you’re using a static VPN, the first step is to remove the static roads from the VPN itself. In the piloting pane, elect Site-to-Site VPN Connection. Highlight your VPN, andthen select static roadways from the navigation pane. Select Edit, and removethe existing routes. It’s best practice to keepa copy of these itineraries, because you’ll be adding themto the transit gateway later.Choose Save, and then Closeto commit your modifications, and return to the Site-to-Site pane. Now, you’ll revise your VPN targets. Your VPN should still be highlighted, so you can navigate toActions, Modify VPN Connection. Under Change Target, choose the drop down menunext to the Target Type, and then select Transit Gateway. Under the drop down menu forTarget Transit Gateway ID, locate and hand-picked Transit Gateway.Save your alterations. Choose Close. You’re returned to the Site-to-Site pane. Now you’ll see your transit gateway is referenced in your VPN items, and your VPN state is set to modify. This takes a few moments to update. When the position of yourVPN registers available, you can navigate to theTransit Gateway Attachments in the sailing pane. Now you’ll see your VPN as an component to your transportation gateway. You can identify your attachmenthere by editing the call discipline, I will reputation mine VPN-1-attachment. The superhighways that you previouslyremoved from the VPN can now be added to the transit gateway. Navigate to the TransitGateway Route Table pane. Make sure that your transitgateway is highlighted, and then, select roadway. Choose Create Routes. under CIDR, supplemented the IP rangeof your on premise structure. Select the drop down menuunder Choose attachment, and then select your VPN.Select Create route. Choose Close, and return to Transit Gateway RouteTables navigation pane. Don’t be surprised if yourroute territory is black hole, as the process of revising your target stops the tunnel briefly. Make sure that you’resending interesting transaction from the customer gatewayto reestablish the VPN. When the passageway is established, the roads territory changes to active. Now we’ll edit the superhighways within the VPC, and site them to the transit gateway. If you transmitting roadways, this stair is unnecessary. Select Route Tables inthe navigation board. Highlight your street table. Then in the Itinerary invoice, adopt Revise Street. Select the routes for the VPN, and then choose the Target drop down menu. Under the Target drop down menu, withdraw existing virtual gateway, choose Transit Gateway, and then select your transport gateway.Choose Save Routes, and then Close. You’ve now successfully moved your VPN from a virtual privategateway to a transit gateway. Thanks for watching andhappy cloud computing from all of us here at AWS.( upbeat music ).