WEBVTT

1
00:00.000 --> 00:05.000
So now that we have some of the groundwork out of the way,

2
00:05.000 --> 00:08.000
let's jump in and take a more detailed look

3
00:08.000 --> 00:13.000
at the private connection offerings from our three major cloud vendors.

4
00:13.000 --> 00:17.000
We'll start with AWS here in this video,

5
00:17.000 --> 00:23.000
but we'll take a look at Microsoft and Google in the following videos.

6
00:23.000 --> 00:27.000
Now, understand that all three of these solutions,

7
00:27.000 --> 00:32.000
just like their descriptions earlier, are going to be very similar.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

7
00:27.000 --> 00:32.000
just like their descriptions earlier, are going to be very similar.

8
00:32.000 --> 00:35.000
So really what we want to focus on are the different components

9
00:35.000 --> 00:39.000
and some of the minor differences between the different solutions.

10
00:39.000 --> 00:41.000
So let's go ahead and jump in.

11
00:41.000 --> 00:47.000
We'll start by taking a look at AWS Direct Connection.

12
00:47.000 --> 00:52.000
So one of the first things we want to mention is that AWS Direct Connection

13
00:52.000 --> 00:57.000
allows administration of all of the SDWAN policies

14
00:57.000 --> 01:00.000
across all of the transports.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

15
01:00.000 --> 01:02.000
What does that mean?

16
01:02.000 --> 01:05.000
Well, it means that we can handle things like our QOS policy

17
01:05.000 --> 01:08.000
and our application aware routing.

18
01:08.000 --> 01:12.000
All of those features of SDWAN are going to be available

19
01:12.000 --> 01:15.000
and controllable by the administrators.

20
01:15.000 --> 01:16.000
Why is that?

21
01:16.000 --> 01:19.000
Well, it's actually quite a simple answer.

22
01:19.000 --> 01:25.000
It's because AWS Direct Connection is simply going to be acting

23
01:25.000 --> 01:28.000
as the underlay connection.

24
01:28.000 --> 01:32.000
This isn't going to be different than any other type of connection.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

24
01:28.000 --> 01:32.000
This isn't going to be different than any other type of connection.

25
01:32.000 --> 01:38.000
This is simply going to be acting as a direct connection to AWS.

26
01:38.000 --> 01:41.000
So let's talk about some of its other attributes.

27
01:41.000 --> 01:47.000
First, this is based on the cloud on-ramp for multi-cloud,

28
01:47.000 --> 01:51.000
specifically the cloud gateway model.

29
01:51.000 --> 01:53.000
If you're not familiar with this,

30
01:53.000 --> 01:57.000
I would encourage you to go back and review the previous skill

31
01:57.000 --> 02:01.000
where we talked about the different cloud on-ramp models.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

31
01:57.000 --> 02:01.000
where we talked about the different cloud on-ramp models.

32
02:01.000 --> 02:05.000
But we'll also see what this entails in a moment

33
02:05.000 --> 02:07.000
when we get to the diagram.

34
02:07.000 --> 02:09.000
Following that model,

35
02:09.000 --> 02:14.000
this means that the SDWAN tunnels are going to be built

36
02:14.000 --> 02:20.000
to the transit VPC, which contains the SDWAN devices.

37
02:20.000 --> 02:25.000
So we're, again, extending the SDWAN environment into AWS.

38
02:25.000 --> 02:31.000
And the idea is we're going to have one of the tunnels run over
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

38
02:25.000 --> 02:31.000
And the idea is we're going to have one of the tunnels run over

39
02:31.000 --> 02:36.000
AWS Direct Connection through the virtual gateway

40
02:36.000 --> 02:40.000
and we'll have possibly -- this is optional, of course --

41
02:40.000 --> 02:44.000
we can have a redundant tunnel run over the internet

42
02:44.000 --> 02:46.000
through an internet gateway.

43
02:46.000 --> 02:51.000
And the really cool thing about this is it is going to be fully automated

44
02:51.000 --> 02:55.000
using cloud on-ramp for multi-cloud,

45
02:55.000 --> 02:58.000
because, again, this is one of those models.

46
02:58.000 --> 03:04.000
And, again, since AWS Direct Connection is only operating as a transport,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

46
02:58.000 --> 03:04.000
And, again, since AWS Direct Connection is only operating as a transport,

47
03:04.000 --> 03:08.000
this, again, means that all of those SDWAN features

48
03:08.000 --> 03:13.000
are going to be available over AWS Direct Connection.

49
03:13.000 --> 03:16.000
So let's go ahead and bring up a diagram here

50
03:16.000 --> 03:19.000
and sort of get an idea what this is going to look like.

51
03:19.000 --> 03:22.000
So let's begin by taking a look at the components

52
03:22.000 --> 03:26.000
that make this part of the cloud gateway model.

53
03:26.000 --> 03:31.000
First, we see here that we do, in fact, have a transit VPC,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

53
03:26.000 --> 03:31.000
First, we see here that we do, in fact, have a transit VPC,

54
03:31.000 --> 03:35.000
which is connecting to various host VPCs,

55
03:35.000 --> 03:41.000
going through the AWS Transit Gateway or the TGW.

56
03:41.000 --> 03:44.000
And then, of course, in our Transit VPC,

57
03:44.000 --> 03:48.000
we have Cisco SDWAN Edge devices,

58
03:48.000 --> 03:51.000
again, up to four redundant pair,

59
03:51.000 --> 03:57.000
and here's the real thing that makes this part of AWS Direct Connection.

60
03:57.000 --> 04:02.000
In this Transit VPC, we have a virtual gateway.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

60
03:57.000 --> 04:02.000
In this Transit VPC, we have a virtual gateway.

61
04:02.000 --> 04:08.000
This virtual gateway is connected to AWS Direct Connect.

62
04:08.000 --> 04:11.000
So this, again, is acting as a separate transport.

63
04:11.000 --> 04:16.000
And what's going to happen then is SDWAN Tunnel 1 here

64
04:16.000 --> 04:19.000
is then going to connect to one color,

65
04:19.000 --> 04:22.000
in this case, possibly green,

66
04:22.000 --> 04:26.000
and SDWAN Tunnel 2 is going to be a different color,

67
04:26.000 --> 04:28.000
again, possibly gold.

68
04:28.000 --> 04:32.000
But either way, we're going to have two separate tunnels
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

68
04:28.000 --> 04:32.000
But either way, we're going to have two separate tunnels

69
04:32.000 --> 04:36.000
going over two separate transports separated by color,

70
04:36.000 --> 04:39.000
one going over the public internet,

71
04:39.000 --> 04:44.000
and the other one going over AWS Direct Connection.

72
04:44.000 --> 04:50.000
So in this video, we took a quick look at AWS Direct Connection.

73
04:50.000 --> 04:53.000
We talked a little bit about some of its attributes,

74
04:53.000 --> 04:56.000
and then we took a look here at this diagram,

75
04:56.000 --> 05:00.000
which represents the different components that would work together
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

76
05:00.000 --> 05:04.000
to make this function as a primary and backup connection,

77
05:04.000 --> 05:07.000
using two different tunnels with two different colors,

78
05:07.000 --> 05:10.000
one going through the public internet,

79
05:10.000 --> 05:14.000
and one going through AWS Direct Connection.

80
05:14.000 --> 05:19.000
Next up, let's take a look at Google's solution for accomplishing

81
05:19.000 --> 05:21.000
pretty much the same thing.