WEBVTT 1 00:00.000 --> 00:07.800 Our last cloud on-ramp design that we're going to be looking at in this skill 2 00:07.800 --> 00:13.000 is the cloud on-ramp for multi-cloud branch connect design. 3 00:13.000 --> 00:19.640 Now, this one differs from the previous cloud gateway design in that it does 4 00:19.640 --> 00:22.000 not use a transit VPC. 5 00:22.000 --> 00:25.300 That of course means that things are going to have to connect a little bit 6 00:25.300 --> 00:28.000 differently and that's going to be our main focus. 7 00:28.000 --> 00:33.000 So let's go ahead and jump in and take a look. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 7 00:28.000 --> 00:33.000 So let's go ahead and jump in and take a look. 8 00:33.000 --> 00:37.320 So the first thing that's probably going to jump out here on this diagram is 9 00:37.320 --> 00:45.430 that this design does not extend the SD-WAN environment into an AWS transit VPC 10 00:45.430 --> 00:46.000 . 11 00:46.000 --> 00:48.000 It's simply not here. 12 00:48.000 --> 00:55.000 We can see that the boundary for the SD-WAN fabric is actually over here. 13 00:55.000 --> 01:02.590 And that means that our SD-WAN environment is using IPsec VPN tunnels to WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 13 00:55.000 --> 01:02.590 And that means that our SD-WAN environment is using IPsec VPN tunnels to 14 01:02.590 --> 01:06.000 connect in to the AWS gateway. 15 01:06.000 --> 01:12.050 And then on the inside of AWS, of course, we're still using those VPC 16 01:12.050 --> 01:20.000 attachments to connect each of our host VPCs to the AWS transit gateway. 17 01:20.000 --> 01:25.000 So of course, this is all about the elimination of that transit VPC. 18 01:25.000 --> 01:30.420 But like we said, without it, it means that the SD-WAN fabric and the host VPCs WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 18 01:25.000 --> 01:30.420 But like we said, without it, it means that the SD-WAN fabric and the host VPCs 19 01:30.420 --> 01:34.000 are connecting directly to that gateway. 20 01:34.000 --> 01:38.000 Now, there's really sort of one big advantage to this design. 21 01:38.000 --> 01:44.000 And that is that it will not incur the AWS expenses. 22 01:44.000 --> 01:51.510 Remember that if we're going to run a transit VPC, it's going to have EC2 23 01:51.510 --> 01:57.000 instances in it that are the SD-WAN edge devices. 24 01:57.000 --> 02:02.920 So there would of course be a cost involved in that, not only to AWS for the EC WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 24 01:57.000 --> 02:02.920 So there would of course be a cost involved in that, not only to AWS for the EC 25 02:02.920 --> 02:10.200 2 instances, but also it's licensing to Cisco, of course, for the SD-WAN edge 26 02:10.200 --> 02:11.000 devices. 27 02:11.000 --> 02:18.000 So without that transit VPC, we are going to have a little bit less expense. 28 02:18.000 --> 02:22.000 However, of course, it does have sort of a big downside. 29 02:22.000 --> 02:30.450 Since this design does not extend the SD-WAN into the AWS environment, well, we WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 29 02:22.000 --> 02:30.450 Since this design does not extend the SD-WAN into the AWS environment, well, we 30 02:30.450 --> 02:32.000 sort of know what that means. 31 02:32.000 --> 02:38.450 It's the opposite of the two previous designs we looked at, those SD-WAN 32 02:38.450 --> 02:41.000 features cannot be used. 33 02:41.000 --> 02:46.130 So we're not going to have things like our application aware routing or any 34 02:46.130 --> 02:49.000 other SD-WAN specific features. 35 02:49.000 --> 02:55.000 SD-WAN is going to be connecting to AWS in a much more traditional fashion. 36 02:55.000 --> 03:01.410 Now we do still have the advantage on the back end that those host VPCs are WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 36 02:55.000 --> 03:01.410 Now we do still have the advantage on the back end that those host VPCs are 37 03:01.410 --> 03:07.000 still using a VPC attachment rather than VPN. 38 03:07.000 --> 03:13.000 So this is still a scalable design on the back end. 39 03:13.000 --> 03:18.000 On the front end, however, we may have a few downsides. 40 03:18.000 --> 03:24.630 The first of those is those dual VPN tunnels that are now going to be going 41 03:24.630 --> 03:29.000 from every customer site over to the gateway. 42 03:29.000 --> 03:36.000 Well, this can actually cause overall higher bandwidth usage in our environment WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 42 03:29.000 --> 03:36.000 Well, this can actually cause overall higher bandwidth usage in our environment 43 03:36.000 --> 03:36.000 . 44 03:36.000 --> 03:39.000 So this can definitely be a downside. 45 03:39.000 --> 03:43.670 Of course, if we have plenty of bandwidth, it's not going to be too much of a 46 03:43.670 --> 03:44.000 concern. 47 03:44.000 --> 03:52.550 The other downside is those IPsec VPNs from AWS to the onsite device, they're 48 03:52.550 --> 03:56.000 all going to be requiring manual configuration. 49 03:56.000 --> 04:01.000 This is not an automated solution for those IPsec VPNs. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 49 03:56.000 --> 04:01.000 This is not an automated solution for those IPsec VPNs. 50 04:01.000 --> 04:05.610 So again, at the end of the day, we have to look at all of these designs, pick 51 04:05.610 --> 04:11.000 the ones that we like the advantages and we can live with the disadvantages. 52 04:11.000 --> 04:16.000 And ultimately pick what we want to use in our environment. 53 04:16.000 --> 04:22.360 So in this video, we focused in on the cloud on ramp for multi cloud branch 54 04:22.360 --> 04:24.000 connect design. 55 04:24.000 --> 04:28.960 The fundamental difference, of course, with this one is we no longer have that 56 04:28.960 --> 04:30.000 transit VPC. WEBVTT X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000 57 04:30.000 --> 04:34.040 The downside is it means we have to have more connections on the front end 58 04:34.040 --> 04:36.000 connecting into the gateway. 59 04:36.000 --> 04:41.320 However, we do have the same scalability on the back end that we had using 60 04:41.320 --> 04:43.000 previous models. 61 04:43.000 --> 04:48.980 So that concludes all of the different design models that we need to discuss in 62 04:48.980 --> 04:54.000 this skill, which leaves us with nothing to do except the challenge. 63 04:54.000 --> 04:58.020 Go ahead and give it a shot and I'll see you in the solution video after the 64 04:58.020 --> 04:59.000 challenge. 65 04:59.000 --> 05:00.040 challenge.