WEBVTT

1
00:00.000 --> 00:08.450
So our first step in getting Google Cloud ready for our VPN is going to be to

2
00:08.450 --> 00:08.960
create some

3
00:08.960 --> 00:15.560
of the necessary components, specifically the VPC and the IP subnet.

4
00:15.560 --> 00:20.040
Now this is where Google Cloud is a little bit different from some of the other

5
00:20.040 --> 00:21.400
cloud providers

6
00:21.400 --> 00:24.680
such as AWS and Microsoft Azure.

7
00:24.680 --> 00:30.140
The difference here is we don't need any special subnet or an extra VPC or
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

7
00:24.680 --> 00:30.140
The difference here is we don't need any special subnet or an extra VPC or

8
00:30.140 --> 00:31.200
anything like

9
00:31.200 --> 00:34.760
that for connecting our VPN gateway.

10
00:34.760 --> 00:40.320
We can connect it directly into this VPC and directly into this subnet.

11
00:40.320 --> 00:45.040
So we actually only need one VPC and one subnet.

12
00:45.040 --> 00:47.520
So this will take very long to accomplish.

13
00:47.520 --> 00:51.830
Let's just go ahead and jump into the Google console and get our VPC and subnet

14
00:51.830 --> 00:52.520
created.

15
00:52.520 --> 00:59.850
So starting here on the Google Cloud console, let's go ahead and go over to our

16
00:59.850 --> 01:00.400
main menu
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

16
00:59.850 --> 01:00.400
main menu

17
01:00.400 --> 01:07.520
here and what we want to do is navigate to VPC network and then VPC networks.

18
01:07.520 --> 01:10.320
Now as you can see right now we don't have any.

19
01:10.320 --> 01:14.920
So we're going to come up here to the top and choose to create a VPC network in

20
01:14.920 --> 01:15.120
our

21
01:15.120 --> 01:17.120
current project.

22
01:17.120 --> 01:21.710
The first thing we have to do is give it a name and just so you're aware,

23
01:21.710 --> 01:22.640
Google Cloud

24
01:22.640 --> 01:26.000
is rather specific about its naming.

25
01:26.000 --> 01:31.920
For example, if I tried to call this VPC one like this, I would get a red box
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

25
01:26.000 --> 01:31.920
For example, if I tried to call this VPC one like this, I would get a red box

26
01:31.920 --> 01:33.040
around it telling

27
01:33.040 --> 01:39.480
me that it only supports lowercase letters, numbers and hyphens.

28
01:39.480 --> 01:43.920
We can't use underscores or uppercase letters, nothing like that.

29
01:43.920 --> 01:48.960
So we're going to have to call this VPC-1 all lowercase.

30
01:48.960 --> 01:51.880
We can of course give it a description if we want.

31
01:51.880 --> 01:57.620
We could change the M2U or the maximum transmission unit and then we get to our

32
01:57.620 --> 01:58.640
subnets.

33
01:58.640 --> 02:02.710
Now we can leave this on custom because that is in fact what we want to do, but
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

33
01:58.640 --> 02:02.710
Now we can leave this on custom because that is in fact what we want to do, but

34
02:02.710 --> 02:03.160
that's

35
02:03.160 --> 02:04.880
what it defaults to.

36
02:04.880 --> 02:09.220
So we scroll down here and it's going to have us create our subnet at the same

37
02:09.220 --> 02:09.800
time as

38
02:09.800 --> 02:11.680
our VPC.

39
02:11.680 --> 02:16.800
Here we'll do the name as subnet 10 and again the same naming convention.

40
02:16.800 --> 02:20.770
That's pretty much consistent through all of Google Cloud that it's just lower

41
02:20.770 --> 02:21.600
case letters,

42
02:21.600 --> 02:23.880
numbers and hyphens.

43
02:23.880 --> 02:27.050
Once again we could give the subnet a description if we wanted like maybe

44
02:27.050 --> 02:27.920
servers or something

45
02:27.920 --> 02:29.720
along those lines.

46
02:29.720 --> 02:33.160
Then of course like most providers we have to choose a region.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

46
02:29.720 --> 02:33.160
Then of course like most providers we have to choose a region.

47
02:33.160 --> 02:37.720
In my case, I deploy things into us east one.

48
02:37.720 --> 02:42.770
That's the closest to my location and then here is where we specify the IPv4

49
02:42.770 --> 02:44.640
subnet range.

50
02:44.640 --> 02:47.040
So remember this is for the subnet.

51
02:47.040 --> 02:53.280
So this is going to be 10.40.10.0/24.

52
02:53.280 --> 02:58.160
Now if we wanted we could create a secondary IPv4 range for this subnet.

53
02:58.160 --> 03:03.720
We could enable things such as private Google access, turn on flow logs, create
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

53
02:58.160 --> 03:03.720
We could enable things such as private Google access, turn on flow logs, create

54
03:03.720 --> 03:04.400
a hybrid

55
03:04.400 --> 03:06.960
subnet which we don't really have a need to do.

56
03:06.960 --> 03:10.250
But if you click on the little question mark here, it'll give you an idea as

57
03:10.250 --> 03:10.880
far as what

58
03:10.880 --> 03:13.480
a hybrid subnet is.

59
03:13.480 --> 03:17.080
But again that's a little bit beyond what we're here to discuss right now.

60
03:17.080 --> 03:21.360
So in our case we can either hit done here or not.

61
03:21.360 --> 03:25.040
In all honesty it doesn't make much difference because if we scroll down notice

62
03:25.040 --> 03:25.760
what the next

63
03:25.760 --> 03:28.320
thing is firewall rules.

64
03:28.320 --> 03:33.720
Well if I hit done all it really does is shrink down the subnet section and
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

64
03:28.320 --> 03:33.720
Well if I hit done all it really does is shrink down the subnet section and

65
03:33.720 --> 03:34.640
still the next

66
03:34.640 --> 03:37.320
thing is firewall rules.

67
03:37.320 --> 03:41.380
So there's not necessarily any reason to hit done in that dialogue box but of

68
03:41.380 --> 03:42.000
course you

69
03:42.000 --> 03:43.800
can if you want.

70
03:43.800 --> 03:48.120
We could also of course add new subnets here if we needed or wanted them.

71
03:48.120 --> 03:52.340
We're going to just be using the one but of course you could create more if

72
03:52.340 --> 03:53.160
needed.

73
03:53.160 --> 03:57.760
Scrolling down here to the firewall rules they do have some firewall rules pre

74
03:57.760 --> 03:58.360
built to

75
03:58.360 --> 04:04.640
allow things like ICMP, RDP, SSH and so on.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

75
03:58.360 --> 04:04.640
allow things like ICMP, RDP, SSH and so on.

76
04:04.640 --> 04:08.120
We can pick and choose which one of these we want to enable but we're not

77
04:08.120 --> 04:08.920
really here to

78
04:08.920 --> 04:13.120
discuss security parameters for firewalls.

79
04:13.120 --> 04:17.320
So for our sake we're just going to go ahead and enable all of the rules.

80
04:17.320 --> 04:19.960
This will allow all the traffic into the subnet.

81
04:19.960 --> 04:23.440
We're not really worried about filtering traffic right now.

82
04:23.440 --> 04:25.560
If we scroll all the way down here.

83
04:25.560 --> 04:29.460
We see we have some other choices such as advanced dynamic routing which we don

84
04:29.460 --> 04:30.200
't need.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

84
04:29.460 --> 04:30.200
't need.

85
04:30.200 --> 04:35.130
We'll just leave this on regional and we can also do legacy or default best

86
04:35.130 --> 04:36.080
path selection

87
04:36.080 --> 04:37.080
mode.

88
04:37.080 --> 04:39.320
We'll leave that as well.

89
04:39.320 --> 04:43.580
There's also DNS configuration which it even tells you right there is optional

90
04:43.580 --> 04:43.800
and in

91
04:43.800 --> 04:48.000
fact we need to enable the DNS API in order to do this.

92
04:48.000 --> 04:51.450
This is all things that are beyond the scope of what we're trying to accomplish

93
04:51.450 --> 04:51.480
.

94
04:51.480 --> 04:55.240
So in our case we'll just go ahead and hit create.

95
04:55.240 --> 04:58.400
It tells us it's creating network VPC one.

96
04:58.400 --> 05:00.920
So after a few moments we end up here.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

96
04:58.400 --> 05:00.920
So after a few moments we end up here.

97
05:00.920 --> 05:05.510
It tells us that it's successfully created network VPC one and we can see up

98
05:05.510 --> 05:06.320
here that it

99
05:06.320 --> 05:07.800
is configured.

100
05:07.800 --> 05:08.800
It has one subnet.

101
05:08.800 --> 05:13.280
We see the M.T.U. and the firewall rules and so on.

102
05:13.280 --> 05:18.270
The other thing we can do is we can come up here, go to subnet's in current

103
05:18.270 --> 05:18.400
project and

104
05:18.400 --> 05:22.000
here we can see that it did in fact create subnet 10.

105
05:22.000 --> 05:29.370
It's in the region U.S. East one attached to VPC one and it has our primary IPv

106
05:29.370 --> 05:30.640
4 range.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

106
05:29.370 --> 05:30.640
4 range.

107
05:30.640 --> 05:35.880
We also see the address that's being used for the Google gateway for traffic to

108
05:35.880 --> 05:36.400
get on

109
05:36.400 --> 05:38.000
and off this network.

110
05:38.000 --> 05:43.600
So as we can see everything here is configured as desired.

111
05:43.600 --> 05:49.430
So in this video we jumped into the Google console and under VPC networks we

112
05:49.430 --> 05:50.160
created our

113
05:50.160 --> 05:56.770
VPC called VPC one and created a subnet subnet 10 with the appropriate IP

114
05:56.770 --> 05:58.080
address range

115
05:58.080 --> 06:02.480
of 10.40.10.0/24.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

115
05:58.080 --> 06:02.480
of 10.40.10.0/24.

116
06:02.480 --> 06:07.440
The next thing we need to do is configure our VPN and peer gateways.

117
06:07.440 --> 06:09.600
So that's what we're going to do in the next video.

118
06:09.600 --> 06:29.600
[silence]