WEBVTT

1
00:00.000 --> 00:08.790
So, in this video, we're going to begin by talking about why you might want

2
00:08.790 --> 00:09.520
private cloud

3
00:09.520 --> 00:11.360
connectivity.

4
00:11.360 --> 00:15.510
Before we can get too far into why you may want it though, we need to make sure

5
00:15.510 --> 00:16.280
that everybody's

6
00:16.280 --> 00:22.040
on the same page of what do we mean by private cloud connectivity.

7
00:22.040 --> 00:26.640
Well, it essentially means that we're going to connect to our various cloud

8
00:26.640 --> 00:27.440
providers,

9
00:27.440 --> 00:32.120
not through the internet, through some other dedicated method.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

9
00:27.440 --> 00:32.120
not through the internet, through some other dedicated method.

10
00:32.120 --> 00:36.490
Now, this, of course, doesn't mean that we're going to get a big long ethernet

11
00:36.490 --> 00:37.400
cable and

12
00:37.400 --> 00:43.310
run it from our business all the way to Amazon or Google or Microsoft, but we

13
00:43.310 --> 00:44.040
are going to

14
00:44.040 --> 00:49.000
be using a service that offers effectively the same thing.

15
00:49.000 --> 00:52.400
And there, of course, are some advantages to doing this.

16
00:52.400 --> 00:55.200
That's what we're here to discuss in this video.

17
00:55.200 --> 00:59.760
But also remember that this is not mutually exclusive.

18
00:59.760 --> 01:05.260
We could certainly use private cloud connectivity to connect to the cloud as
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

18
00:59.760 --> 01:05.260
We could certainly use private cloud connectivity to connect to the cloud as

19
01:05.260 --> 01:07.120
our main connection,

20
01:07.120 --> 01:11.120
and we could still use an internet connection as a backup.

21
01:11.120 --> 01:14.400
So in other words, a VPN over the internet.

22
01:14.400 --> 01:16.520
So again, they're not mutually exclusive.

23
01:16.520 --> 01:18.400
We can certainly do both.

24
01:18.400 --> 01:23.120
But let's jump in and take a more detailed look at some of the advantages of

25
01:23.120 --> 01:24.120
private cloud

26
01:24.120 --> 01:29.760
connectivity over just using the public internet.

27
01:29.760 --> 01:36.400
So as we've discussed many times in this course, public internet access does
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

27
01:29.760 --> 01:36.400
So as we've discussed many times in this course, public internet access does

28
01:36.400 --> 01:37.800
offer a very cost

29
01:37.800 --> 01:42.240
effective way to connect to our cloud providers.

30
01:42.240 --> 01:47.720
But there are, of course, a few downsides to public internet access.

31
01:47.720 --> 01:51.720
So what are those downsides that we want to be concerned with?

32
01:51.720 --> 01:57.300
Well, probably one of the biggest problems is that there is absolutely no

33
01:57.300 --> 01:58.880
native security.

34
01:58.880 --> 02:01.640
Now of course, we have ways to fix this.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

34
01:58.880 --> 02:01.640
Now of course, we have ways to fix this.

35
02:01.640 --> 02:05.000
And we've discussed it throughout this course so far.

36
02:05.000 --> 02:09.120
We can of course do an IPsec VPN.

37
02:09.120 --> 02:13.460
So there are definitely ways to work with this, but it is something we have to

38
02:13.460 --> 02:14.760
work with.

39
02:14.760 --> 02:20.200
If we have a private cloud connection, this may not be as much of a concern.

40
02:20.200 --> 02:26.880
Now SD-WAN will do this for us either way, but this is still a disadvantage to

41
02:26.880 --> 02:28.000
using internet

42
02:28.000 --> 02:29.520
access.

43
02:29.520 --> 02:37.070
Another big one is we have absolutely no traffic control or QOS quality of
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

43
02:29.520 --> 02:37.070
Another big one is we have absolutely no traffic control or QOS quality of

44
02:37.070 --> 02:38.400
service.

45
02:38.400 --> 02:44.600
We have no way of prioritizing traffic over other traffic and so on.

46
02:44.600 --> 02:49.400
Now within our own traffic path, we of course can.

47
02:49.400 --> 02:53.560
We can prioritize our own traffic over other traffic.

48
02:53.560 --> 02:58.890
What we cannot do is prioritize our traffic over other people's traffic and so

49
02:58.890 --> 02:59.240
on.

50
02:59.240 --> 03:04.000
And as such, this becomes a first-come, first-serve model.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

50
02:59.240 --> 03:04.000
And as such, this becomes a first-come, first-serve model.

51
03:04.000 --> 03:08.600
That's not always the best solution for our cloud connectivity.

52
03:08.600 --> 03:14.040
And something else to keep in mind that since most companies are going to just

53
03:14.040 --> 03:14.680
have the

54
03:14.680 --> 03:19.380
one internet connection, we're going to be sharing that traffic load of all the

55
03:19.380 --> 03:19.880
traffic

56
03:19.880 --> 03:25.320
going to the cloud and our normal traffic going to the internet.

57
03:25.320 --> 03:29.530
So these two types of traffic are now going to be sharing that one connection

58
03:29.530 --> 03:29.880
where if

59
03:29.880 --> 03:35.470
we have private connectivity, then that will generally be a dedicated circuit
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

59
03:29.880 --> 03:35.470
we have private connectivity, then that will generally be a dedicated circuit

60
03:35.470 --> 03:36.240
going just

61
03:36.240 --> 03:38.440
to our cloud provider.

62
03:38.440 --> 03:44.210
So let's talk a little bit more specifically about those advantages that we get

63
03:44.210 --> 03:44.760
with a

64
03:44.760 --> 03:46.800
private connection.

65
03:46.800 --> 03:49.960
So one of the big ones is dependability.

66
03:49.960 --> 03:54.860
Often, private connections will come with a level of guarantee for depend

67
03:54.860 --> 03:55.960
ability, also

68
03:55.960 --> 03:58.040
predictability.

69
03:58.040 --> 04:02.430
And this in a way comes back to the no traffic control and the shared traffic
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

69
03:58.040 --> 04:02.430
And this in a way comes back to the no traffic control and the shared traffic

70
04:02.430 --> 04:03.400
load problems

71
04:03.400 --> 04:05.320
we discussed up here.

72
04:05.320 --> 04:09.200
If it's dedicated access, it's going to be predictable access.

73
04:09.200 --> 04:14.210
It's not going to be competing with other customers' traffic or your own

74
04:14.210 --> 04:15.280
internet-based

75
04:15.280 --> 04:16.280
traffic.

76
04:16.280 --> 04:20.560
It's also naturally going to have a built-in level of security.

77
04:20.560 --> 04:24.840
And again, it may not be the full level of security we want, but if our traffic

78
04:24.840 --> 04:26.200
is 100%

79
04:26.200 --> 04:31.540
completely separate from every other customer's traffic, well, that by itself
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

79
04:26.200 --> 04:31.540
completely separate from every other customer's traffic, well, that by itself

80
04:31.540 --> 04:32.640
lends a certain

81
04:32.640 --> 04:33.960
level of security.

82
04:33.960 --> 04:38.560
Now, there is a certain amount of, "Do we trust the provider?"

83
04:38.560 --> 04:42.680
And that's why we probably still want to use encryption such as IPsec.

84
04:42.680 --> 04:47.520
However, it's still going to be a certain level of security higher than just

85
04:47.520 --> 04:48.440
plain internet

86
04:48.440 --> 04:49.760
access.

87
04:49.760 --> 04:53.900
These are generally going to be very low latency connections, again, partially

88
04:53.900 --> 04:54.520
because they're

89
04:54.520 --> 04:56.680
not sharing traffic.

90
04:56.680 --> 05:00.960
And since they're not sharing traffic and it is a dedicated connection, this
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

90
04:56.680 --> 05:00.960
And since they're not sharing traffic and it is a dedicated connection, this

91
05:00.960 --> 05:01.480
means we

92
05:01.480 --> 05:07.870
do have that total traffic control and complete control over our quality of

93
05:07.870 --> 05:08.960
service.

94
05:08.960 --> 05:13.160
So as cool as all of this sounds, how do we go about actually setting up

95
05:13.160 --> 05:14.920
private connectivity?

96
05:14.920 --> 05:19.830
Well, the answer to that is there are actually several popular methods that we

97
05:19.830 --> 05:20.480
can use to

98
05:20.480 --> 05:24.520
establish private access to these clouds.

99
05:24.520 --> 05:27.870
Most of them, of course, are going to depend on your cloud provider, so let's

100
05:27.870 --> 05:28.320
go ahead

101
05:28.320 --> 05:31.080
and start with AWS.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

101
05:28.320 --> 05:31.080
and start with AWS.

102
05:31.080 --> 05:36.040
So AWS offers a product called DirectConnect.

103
05:36.040 --> 05:38.280
And some of its attributes.

104
05:38.280 --> 05:46.350
This enables a secure, fast network connection between your infrastructure and

105
05:46.350 --> 05:47.120
AWS.

106
05:47.120 --> 05:51.920
Of course, this is without using the public internet.

107
05:51.920 --> 05:54.240
That's the whole point of this.

108
05:54.240 --> 05:59.090
And there's really sort of two different ways that we can get AWS DirectConnect

109
05:59.090 --> 05:59.120
.

110
05:59.120 --> 06:04.890
We can choose an AWS DirectConnect delivery partner, which is a third party,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

110
05:59.120 --> 06:04.890
We can choose an AWS DirectConnect delivery partner, which is a third party,

111
06:04.890 --> 06:05.600
which is

112
06:05.600 --> 06:10.240
going to connect between our network and AWS.

113
06:10.240 --> 06:16.160
Or we can, of course, choose a dedicated connection from AWS themselves.

114
06:16.160 --> 06:20.240
Some of this is, of course, going to come down to availability.

115
06:20.240 --> 06:25.160
What can you get in your location around the world?

116
06:25.160 --> 06:29.500
And just to throw this out there, that is sort of a disadvantage of private

117
06:29.500 --> 06:30.400
connectivity
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

117
06:29.500 --> 06:30.400
connectivity

118
06:30.400 --> 06:31.960
in general.

119
06:31.960 --> 06:34.840
This may or may not be available everywhere.

120
06:34.840 --> 06:39.010
Now, there are some things we could do to maybe work around that that we'll

121
06:39.010 --> 06:40.040
discuss towards

122
06:40.040 --> 06:41.920
the end of this skill.

123
06:41.920 --> 06:46.000
But in the meantime, we also have an offering from Azure.

124
06:46.000 --> 06:49.840
So we have something called Azure Express route.

125
06:49.840 --> 06:52.840
This, of course, serves a very similar function.

126
06:52.840 --> 06:58.200
It allows us to establish that private connection between, again, the on-prem

127
06:58.200 --> 06:59.400
infrastructure

128
06:59.400 --> 07:02.120
and Azure data centers.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

128
06:59.400 --> 07:02.120
and Azure data centers.

129
07:02.120 --> 07:06.560
And this one is going to be done through a connectivity provider.

130
07:06.560 --> 07:11.120
And of course, they're going to create that dedicated and secure network

131
07:11.120 --> 07:11.400
connection.

132
07:11.400 --> 07:16.440
On the Google side of things, we have Cloud Interconnect.

133
07:16.440 --> 07:20.640
Once again, the whole goal here is it creates that private connection between

134
07:20.640 --> 07:21.440
your on-prem

135
07:21.440 --> 07:26.000
environment and the Google Cloud platform.

136
07:26.000 --> 07:30.880
Once again, here we can choose between a dedicated or partner interconnects.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

136
07:26.000 --> 07:30.880
Once again, here we can choose between a dedicated or partner interconnects.

137
07:30.880 --> 07:35.800
But either way, it's going to be a dependable secure connection.

138
07:35.800 --> 07:40.440
Just as a quick note here, I want you to notice how similar all of these

139
07:40.440 --> 07:41.640
descriptions were

140
07:41.640 --> 07:46.680
for all three of these products from the three different major cloud providers.

141
07:46.680 --> 07:52.040
The reason I'm pointing this out is I took this information almost directly off

142
07:52.040 --> 07:52.400
their

143
07:52.400 --> 07:53.640
web pages.

144
07:53.640 --> 07:56.640
Now, why am I pointing that out?

145
07:56.640 --> 08:00.040
They're all offering essentially the same service.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

145
07:56.640 --> 08:00.040
They're all offering essentially the same service.

146
08:00.040 --> 08:02.120
So just keep that in mind.

147
08:02.120 --> 08:06.040
Do they vary slightly between offerings and exactly how they work?

148
08:06.040 --> 08:07.640
Well, of course they do.

149
08:07.640 --> 08:12.590
But overall, all three of these solutions are going to offer the same basic

150
08:12.590 --> 08:13.560
function.

151
08:13.560 --> 08:19.320
Now one final sort of generic option would be carrier Ethernet services.

152
08:19.320 --> 08:24.630
This is commonly going to be offered by your ISP or your internet service

153
08:24.630 --> 08:25.240
provider where

154
08:25.240 --> 08:30.300
they'll offer an ethernet service that's going to connect again your local
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

154
08:25.240 --> 08:30.300
they'll offer an ethernet service that's going to connect again your local

155
08:30.300 --> 08:32.040
network to various

156
08:32.040 --> 08:33.680
public clouds.

157
08:33.680 --> 08:37.960
And of course, they'll usually offer this service for all of the major

158
08:37.960 --> 08:38.920
providers.

159
08:38.920 --> 08:44.520
So Amazon, Microsoft and Google would certainly be included in that list.

160
08:44.520 --> 08:48.240
And once again, just like these other options, these are going to generally

161
08:48.240 --> 08:48.960
offer fast and

162
08:48.960 --> 08:50.880
reliable connections.

163
08:50.880 --> 08:56.140
And they're often going to offer a SLA or a service level agreement.

164
08:56.140 --> 09:00.280
And that's going to actually be a guarantee on performance.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

164
08:56.140 --> 09:00.280
And that's going to actually be a guarantee on performance.

165
09:00.280 --> 09:04.250
Now of course, what that means is if they don't meet the SLA, oftentimes there

166
09:04.250 --> 09:04.680
will be

167
09:04.680 --> 09:08.600
a penalty built in for the service provider.

168
09:08.600 --> 09:12.530
Sometimes you get a discount on your monthly bill or you don't pay for the time

169
09:12.530 --> 09:12.960
that the

170
09:12.960 --> 09:15.720
network wasn't meeting the SLA.

171
09:15.720 --> 09:20.480
That's of course all going to be handled through contracts.

172
09:20.480 --> 09:26.670
So in this video, we just wanted to jump in and start discussing private cloud

173
09:26.670 --> 09:28.160
connectivity.

174
09:28.160 --> 09:29.160
What is it?

175
09:29.160 --> 09:32.240
We covered that just during the introduction because that's fairly
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

175
09:29.160 --> 09:32.240
We covered that just during the introduction because that's fairly

176
09:32.240 --> 09:33.240
straightforward.

177
09:33.240 --> 09:39.200
But what are some of the advantages or disadvantages of using a private

178
09:39.200 --> 09:39.520
connection?

179
09:39.520 --> 09:43.130
Private connections are of course generally more secure, more reliable, more

180
09:43.130 --> 09:43.920
dependable,

181
09:43.920 --> 09:45.960
lower latency and so on.

182
09:45.960 --> 09:49.360
However, they may not be available everywhere.

183
09:49.360 --> 09:53.480
And in some cases, they may be more expensive.

184
09:53.480 --> 09:58.050
General Internet access of course is available almost everywhere and certainly

185
09:58.050 --> 09:59.040
available anywhere

186
09:59.040 --> 10:03.960
we want to access the cloud or well, it's probably not even an option.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

186
09:59.040 --> 10:03.960
we want to access the cloud or well, it's probably not even an option.

187
10:03.960 --> 10:08.090
But all of this said, before we can start using this, particularly if we're

188
10:08.090 --> 10:08.640
going to

189
10:08.640 --> 10:14.490
use a primary and a backup solution, in other words, maybe using our private

190
10:14.490 --> 10:15.600
connectivity

191
10:15.600 --> 10:21.770
for our primary connection and using the Internet as a backup, we need to talk

192
10:21.770 --> 10:22.640
about something

193
10:22.640 --> 10:26.480
called transport locators or T-locks.

194
10:26.480 --> 10:29.640
So let's go ahead and jump into that in the next video.