WEBVTT

1
00:00.000 --> 00:07.710
For the next three videos, we're going to be taking a look at the various

2
00:07.710 --> 00:08.300
performance

3
00:08.300 --> 00:14.310
and redundancy options available from our three major cloud providers starting

4
00:14.310 --> 00:14.960
in this

5
00:14.960 --> 00:18.720
video with Amazon's AWS.

6
00:18.720 --> 00:23.960
Now just to be very clear, this is just an overview of these offerings.

7
00:23.960 --> 00:28.360
We don't have to be experts on the offerings from these providers.

8
00:28.360 --> 00:32.430
We just want to be familiar with what they have available and sort of what the
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

8
00:28.360 --> 00:32.430
We just want to be familiar with what they have available and sort of what the

9
00:32.430 --> 00:33.040
different

10
00:33.040 --> 00:36.000
features are called from the different providers.

11
00:36.000 --> 00:40.890
So let's go ahead and jump in taking a look at some of the redundancy options

12
00:40.890 --> 00:41.360
available

13
00:41.360 --> 00:46.280
from Amazon's AWS.

14
00:46.280 --> 00:52.640
So to be clear, the AWS infrastructure has actually a lot of redundancy built

15
00:52.640 --> 00:53.240
in.

16
00:53.240 --> 00:55.920
We're just going to be looking at some parts of that.

17
00:55.920 --> 01:00.760
The first part of that redundancy is their hierarchical structure.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

17
00:55.920 --> 01:00.760
The first part of that redundancy is their hierarchical structure.

18
01:00.760 --> 01:04.800
The first level of that is called the region.

19
01:04.800 --> 01:12.520
The region is a completely self-sufficient and completely independent component

20
01:12.520 --> 01:12.960
that if

21
01:12.960 --> 01:18.480
one region were to fail, it won't affect anything in the other regions.

22
01:18.480 --> 01:21.280
So this is our first level of redundancy.

23
01:21.280 --> 01:26.840
And we can actually hop over to AWS and we can actually see right up here that

24
01:26.840 --> 01:27.360
you can

25
01:27.360 --> 01:31.680
choose different regions based on where you're located.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

25
01:27.360 --> 01:31.680
choose different regions based on where you're located.

26
01:31.680 --> 01:35.760
So sometimes we'll pick a region based on performance as far as what's closest

27
01:35.760 --> 01:36.960
to us.

28
01:36.960 --> 01:41.420
And sometimes we might want to pick different regions just for their geographic

29
01:41.420 --> 01:42.720
dispersity.

30
01:42.720 --> 01:47.440
That way we don't have anything too close if something major were to happen.

31
01:47.440 --> 01:51.880
But this is your first level of redundancy in AWS.

32
01:51.880 --> 01:58.480
The second level of redundancy is the availability zone or the AZ.

33
01:58.480 --> 02:02.280
The availability zones are inside each region.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

33
01:58.480 --> 02:02.280
The availability zones are inside each region.

34
02:02.280 --> 02:06.960
So the region is broken up by availability zone effectively.

35
02:06.960 --> 02:11.280
Each availability zone is in and of itself a complete data center.

36
02:11.280 --> 02:15.700
It has its own redundant power, its own redundant cooling, its own redundant

37
02:15.700 --> 02:17.400
network connectivity.

38
02:17.400 --> 02:23.430
So each one has all of the features that we talked about in our previous video

39
02:23.430 --> 02:23.680
that we

40
02:23.680 --> 02:27.080
as a customer would want to provide to our data centers.

41
02:27.080 --> 02:31.040
Amazon is doing all of that if not more.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

41
02:27.080 --> 02:31.040
Amazon is doing all of that if not more.

42
02:31.040 --> 02:35.460
Now depending on the resource you're actually deploying, you're either going to

43
02:35.460 --> 02:35.760
choose a

44
02:35.760 --> 02:41.200
region or an availability zone depending on the object type.

45
02:41.200 --> 02:47.810
So for example, the AWS, internet and transit gateways both have regional

46
02:47.810 --> 02:49.160
redundancy, which

47
02:49.160 --> 02:53.210
means when you deploy one of those items, you're going to choose a region to

48
02:53.210 --> 02:53.600
put it

49
02:53.600 --> 02:55.080
in.

50
02:55.080 --> 03:01.040
Things like your SD-WAN, edge routers, things like subnets, servers, these are
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

50
02:55.080 --> 03:01.040
Things like your SD-WAN, edge routers, things like subnets, servers, these are

51
03:01.040 --> 03:01.480
going to

52
03:01.480 --> 03:04.480
get assigned to an availability zone.

53
03:04.480 --> 03:11.160
And keep in mind that just like our regions, any failures in that availability

54
03:11.160 --> 03:11.400
zone are

55
03:11.400 --> 03:15.520
only going to affect the things in that zone.

56
03:15.520 --> 03:20.880
So what we really want to do for these type of items, if at all possible, to

57
03:20.880 --> 03:21.600
have good

58
03:21.600 --> 03:26.970
redundancy, we're going to put those resources into multiple different

59
03:26.970 --> 03:28.800
availability zones.

60
03:28.800 --> 03:32.940
So again, if I'm deploying multiple routers, multiple servers and so on, we
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

60
03:28.800 --> 03:32.940
So again, if I'm deploying multiple routers, multiple servers and so on, we

61
03:32.940 --> 03:33.720
want to make

62
03:33.720 --> 03:37.760
sure that we're putting them in different availability zones.

63
03:37.760 --> 03:41.470
In order to ensure that the traffic gets to these different servers in

64
03:41.470 --> 03:42.880
different availability

65
03:42.880 --> 03:50.470
zones effectively, AWS has a feature called elastic load balancing, which dist

66
03:50.470 --> 03:51.840
ributes incoming

67
03:51.840 --> 03:57.800
application traffic across multiple endpoints and most importantly, in

68
03:57.800 --> 03:59.440
different availability

69
03:59.440 --> 04:01.520
zones.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

69
03:59.440 --> 04:01.520
zones.

70
04:01.520 --> 04:06.440
So this is an idea of what this would look like graphically.

71
04:06.440 --> 04:11.980
In this case, we're really only using a single AWS region on this discussion,

72
04:11.980 --> 04:12.400
but we have

73
04:12.400 --> 04:16.720
a single region here and then we have multiple zones.

74
04:16.720 --> 04:19.080
So over here, we have zone one down here.

75
04:19.080 --> 04:25.940
We have zone two and we have a transit VPC deployed, which also has routers for

76
04:25.940 --> 04:27.080
redundancy

77
04:27.080 --> 04:30.960
in zone one and zone two.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

77
04:27.080 --> 04:30.960
in zone one and zone two.

78
04:30.960 --> 04:35.230
So we're providing redundancy here, but all of these would go through the same

79
04:35.230 --> 04:35.960
AWS transit

80
04:35.960 --> 04:40.760
gateway, which again has its redundancy per the region.

81
04:40.760 --> 04:44.800
Now there's actually sort of two ways to deploy this model.

82
04:44.800 --> 04:49.720
One is we could use cloud on ramp for multi cloud.

83
04:49.720 --> 04:55.950
This actually allows for multiple connections to multiple clouds with SD WAN,

84
04:55.950 --> 04:57.320
including different

85
04:57.320 --> 04:59.480
AWS regions.

86
04:59.480 --> 05:03.590
What you would actually do for this design is again, like we just saw, you
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

86
04:59.480 --> 05:03.590
What you would actually do for this design is again, like we just saw, you

87
05:03.590 --> 05:04.080
would have a

88
05:04.080 --> 05:09.440
transit VPC, you have a pair of SD WAN edges.

89
05:09.440 --> 05:13.800
Again, the idea being that we're going to deploy these into different

90
05:13.800 --> 05:15.960
availability zones.

91
05:15.960 --> 05:18.360
So that's going to provide some redundancy.

92
05:18.360 --> 05:25.360
And then we use IP sec tunnels to connect to that regional transit gateway.

93
05:25.360 --> 05:30.150
Now if for some reason you don't want to use cloud on ramp, we can still
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

93
05:25.360 --> 05:30.150
Now if for some reason you don't want to use cloud on ramp, we can still

94
05:30.150 --> 05:32.560
configure redundancy,

95
05:32.560 --> 05:35.160
doing it pretty much the same way.

96
05:35.160 --> 05:37.640
You're going to see here that these are all sort of the same.

97
05:37.640 --> 05:40.320
We're still going to have a transit VPC.

98
05:40.320 --> 05:44.040
We still deploy a pair of SD WAN edge routers.

99
05:44.040 --> 05:47.670
Here we're going to deploy them though from the marketplace, not cloud on ramp

100
05:47.670 --> 05:48.240
deploying

101
05:48.240 --> 05:49.640
them.

102
05:49.640 --> 05:53.760
And we're going to still deploy them in different availability zones.

103
05:53.760 --> 05:58.760
We're also still going to connect them with IP sec to the transit gateway.

104
05:58.760 --> 06:04.700
The main difference here is we're then going to use BGP to control the routing
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

104
05:58.760 --> 06:04.700
The main difference here is we're then going to use BGP to control the routing

105
06:04.700 --> 06:05.080
across

106
06:05.080 --> 06:06.960
these available tunnels.

107
06:06.960 --> 06:09.600
So this is just sort of the way of doing it manually.

108
06:09.600 --> 06:13.870
If for whatever reason, you don't want to use cloud on ramp for multi cloud to

109
06:13.870 --> 06:14.360
configure

110
06:14.360 --> 06:15.880
this.

111
06:15.880 --> 06:20.090
So in this video, we just jumped in and took a look at the hierarchical

112
06:20.090 --> 06:21.160
structure that

113
06:21.160 --> 06:24.160
AWS implements for their redundancy.

114
06:24.160 --> 06:28.500
And we talked a little bit about how we could deploy that and what our design

115
06:28.500 --> 06:29.240
models might

116
06:29.240 --> 06:30.680
look like.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

116
06:29.240 --> 06:30.680
look like.

117
06:30.680 --> 06:34.740
Next up, let's take a look at the similar things that we have available in

118
06:34.740 --> 06:35.560
Microsoft's

119
06:35.560 --> 06:36.200
Azure.

120
06:36.200 --> 06:46.200
[BLANK_AUDIO]