WEBVTT - This file was automatically generated by VIMEO

0
00:00:07.200 --> 00:00:10.500
In this video, we're going to explore subnets and routing in your VPC.

1
00:00:12.400 --> 00:00:15.600
A subnet is a range of IP addresses that you can use inside your

2
00:00:15.600 --> 00:00:16.100
 VPC.

3
00:00:16.800 --> 00:00:19.100
It is a subset or a slice of your

4
00:00:19.100 --> 00:00:22.500
 overall VPC address range. If you recall the default

5
00:00:22.500 --> 00:00:25.900
 VPC in AWS was a slash 16. This

6
00:00:25.900 --> 00:00:30.200
 means you can partition the 65,534 available

7
00:00:29.200 --> 00:00:33.100
 addresses into multiple subnets. This

8
00:00:32.100 --> 00:00:35.800
 is called subnetting each subnet must

9
00:00:35.800 --> 00:00:38.900
 live within one availability Zone in AZ

10
00:00:38.900 --> 00:00:41.300
 as it's more commonly called. It's just

11
00:00:41.300 --> 00:00:44.800
 an isolated location inside a region like Eastern United

12
00:00:44.800 --> 00:00:47.400
 States. Multiple. AZ are

13
00:00:47.400 --> 00:00:48.100
 used for availability.

14
00:00:49.700 --> 00:00:53.200
Route tables contain rules which AWS calls

15
00:00:52.200 --> 00:00:55.600
 routes. They govern where your network traffic

16
00:00:55.600 --> 00:00:58.700
 will go this traffic can either be from subnets or

17
00:00:58.700 --> 00:01:01.500
 from gateways a rule consists of a destination

18
00:01:01.500 --> 00:01:04.400
 and a target a destination is usually an IP

19
00:01:04.400 --> 00:01:07.200
 address or a range while the target is where the traffic is

20
00:01:07.200 --> 00:01:07.700
 being sent.

21
00:01:08.500 --> 00:01:11.400
Route tables will have subnets associated with them to govern where

22
00:01:11.400 --> 00:01:12.600
 Network packets can be sent.

23
00:01:13.900 --> 00:01:16.400
Okay. So for this video what we

24
00:01:16.400 --> 00:01:19.200
 plan to do is we're gonna review subnets and

25
00:01:19.200 --> 00:01:22.900
 Route table components inside the AWS console like with

26
00:01:22.900 --> 00:01:25.400
 vpcs. You will learn where to find the resources

27
00:01:25.400 --> 00:01:27.900
 and review some of the attributes associated with them.

28
00:01:28.700 --> 00:01:31.400
After that, we will head back over to a terminal and

29
00:01:31.400 --> 00:01:34.800
 explore your subnet and Route terraform files. Okay,

30
00:01:34.800 --> 00:01:35.600
 let's get started.

31
00:01:36.900 --> 00:01:39.600
Okay. So here we are back in the AWS console

32
00:01:39.600 --> 00:01:42.700
 and we're gonna go back up to VPC

33
00:01:42.700 --> 00:01:45.200
 since routing and subnets are

34
00:01:45.200 --> 00:01:48.400
 both a part of the VPC umbrella. So I'll just click on recently

35
00:01:48.400 --> 00:01:50.500
 visited here. I'm gonna go to VPC.

36
00:01:53.700 --> 00:01:56.100
Okay. So the first thing we want to do is we're going

37
00:01:56.100 --> 00:01:59.500
 to click on subnets. We'll talk about subnets first then route tables.

38
00:02:00.200 --> 00:02:03.600
So click on subnets as you see here this four subnets

39
00:02:03.600 --> 00:02:06.300
 that come up here. These are the four default subnets that you

40
00:02:06.300 --> 00:02:09.100
 will get assigned when you create your account. The reason why

41
00:02:09.100 --> 00:02:12.400
 this 4 is because we're in the US West two region, you can see up

42
00:02:12.400 --> 00:02:15.400
 here with it's as organ and there are

43
00:02:15.400 --> 00:02:18.600
 four availability zones a b c

44
00:02:18.600 --> 00:02:21.300
 and d and so this is by Design because

45
00:02:21.300 --> 00:02:24.400
 obviously you don't want all your workloads in one subnet because

46
00:02:24.400 --> 00:02:27.600
 if Amazon lost one of these availability zones then

47
00:02:27.600 --> 00:02:30.400
 anything you have running in that availability zone is pretty

48
00:02:30.400 --> 00:02:33.100
 much gone as well. So you want to spread your

49
00:02:33.100 --> 00:02:36.200
 workload amongst all the subnets as you possibly can.

50
00:02:36.800 --> 00:02:39.100
So if we look here the biggest thing one of the

51
00:02:39.100 --> 00:02:43.200
 large things to take away from here is you can see the ipv4 cider

52
00:02:42.200 --> 00:02:45.100
 range column right here as you can

53
00:02:45.100 --> 00:02:48.700
 see over here in The ipv4 Cider column here that these

54
00:02:48.700 --> 00:02:52.100
 all for these subnets have different IP

55
00:02:51.100 --> 00:02:54.300
 address ranges when they're where they're also

56
00:02:54.300 --> 00:02:57.200
 denoted by the slash 20 slash 20 means

57
00:02:57.200 --> 00:03:00.200
 around 4,000 IP addresses. So Amazon when they created

58
00:03:00.200 --> 00:03:03.700
 this Force basically took our 65,000 plus addresses

59
00:03:03.700 --> 00:03:07.700
 and they carved out about 16,000 of

60
00:03:07.700 --> 00:03:08.100
 those here.

61
00:03:08.900 --> 00:03:11.300
And as you can see, if you scroll over here to the right, you

62
00:03:11.300 --> 00:03:14.800
 can see that those 4,091 IP addresses and you

63
00:03:14.800 --> 00:03:16.600
 the availability zones I was talking about.

64
00:03:17.900 --> 00:03:21.200
And the route tables are associated with this network

65
00:03:20.200 --> 00:03:23.500
 ACLS. We're not going to talk about that here.

66
00:03:23.500 --> 00:03:26.400
 But ACLS are just like what you think they're Access Control.

67
00:03:26.400 --> 00:03:29.700
 This is allowing deny rules, and these

68
00:03:29.700 --> 00:03:31.300
 are default subnet.

69
00:03:32.100 --> 00:03:35.400
So let's go back over here to the top and let's go

70
00:03:35.400 --> 00:03:38.100
 ahead and drill down on one of these subnets to get a little bit more

71
00:03:38.100 --> 00:03:41.000
 details. I'll just pick this second one from the top.

72
00:03:41.900 --> 00:03:44.300
I mean move this up here. So it's easier to

73
00:03:44.300 --> 00:03:44.700
 see.

74
00:03:45.700 --> 00:03:46.100
Okay.

75
00:03:47.200 --> 00:03:50.600
So here we can see now we have the top. We have

76
00:03:50.600 --> 00:03:53.300
 our details pane like we normally saw like

77
00:03:53.300 --> 00:03:55.900
 in VPC and we'll see that is in other ones we go.

78
00:03:56.600 --> 00:04:00.000
You have these top tabs up here details flow

79
00:03:59.400 --> 00:04:02.600
 logs route table ACLS cider

80
00:04:02.600 --> 00:04:05.700
 reservations sharing and then tags. We're only

81
00:04:05.700 --> 00:04:09.300
 going to talk about the details and the route table here before

82
00:04:08.300 --> 00:04:11.500
 we move on to the right tables. It's only

83
00:04:11.500 --> 00:04:15.100
 thing really pertinent as as we get into this. So here

84
00:04:14.100 --> 00:04:18.100
 we have our subnet ID subnet

85
00:04:17.100 --> 00:04:20.300
 Dash and then the character set afterwards, which

86
00:04:20.300 --> 00:04:23.600
 is very common as you see we talked about the available IP

87
00:04:23.600 --> 00:04:23.900
 addresses.

88
00:04:24.700 --> 00:04:27.200
This one I picked happens to be in the US

89
00:04:27.200 --> 00:04:29.200
 West to see availability Zone.

90
00:04:29.800 --> 00:04:32.100
And as you can see this one, this IP address

91
00:04:32.100 --> 00:04:35.700
 range is the 172 31 0.0 slash

92
00:04:35.700 --> 00:04:36.100
 20.

93
00:04:36.900 --> 00:04:39.200
And here where you can see we're Associated to this

94
00:04:39.200 --> 00:04:42.200
 VPC. This is the same default VPC. We learned about

95
00:04:42.200 --> 00:04:42.600
 earlier.

96
00:04:44.200 --> 00:04:47.200
And as you see it is a route table associated with this is also the

97
00:04:47.200 --> 00:04:52.300
 default route table that was created for us too. So that

98
00:04:51.300 --> 00:04:54.300
 is about all I'll go ahead and click on

99
00:04:54.300 --> 00:04:57.300
 Route table actually just to show you that you see that

100
00:04:57.300 --> 00:05:00.400
 and then there's the routes that are associated with this route table,

101
00:05:00.400 --> 00:05:03.100
 but let's go ahead and go over to the

102
00:05:03.100 --> 00:05:06.400
 route table first to view this more. So that's really

103
00:05:06.400 --> 00:05:09.300
 it for subnets for right now. Let's go ahead

104
00:05:09.300 --> 00:05:12.000
 and click on Route tables here to your left and the pain

105
00:05:12.600 --> 00:05:13.500
Go ahead and click on that.

106
00:05:14.600 --> 00:05:17.200
Since we had that subnet already highlighted when we come over

107
00:05:17.200 --> 00:05:20.200
 here, it's already checked the route table for us. There's only

108
00:05:20.200 --> 00:05:23.500
 one route table. If I uncheck this you can see there's only one at the

109
00:05:23.500 --> 00:05:25.600
 top here. You can see that we have

110
00:05:26.800 --> 00:05:29.200
a orange button up here

111
00:05:29.200 --> 00:05:32.200
 that this is the wizard that you can use to create your

112
00:05:32.200 --> 00:05:35.500
 own route table over here this actions and this

113
00:05:35.500 --> 00:05:36.300
 is where you can do.

114
00:05:38.200 --> 00:05:41.600
You can do editing or you can do deletion of whatever route

115
00:05:41.600 --> 00:05:42.400
 table you have selected.

116
00:05:43.400 --> 00:05:46.700
Since we are using the command line and infrastructure's

117
00:05:46.700 --> 00:05:49.700
 code tool called terraform to do this. We aren't

118
00:05:49.700 --> 00:05:52.700
 going to be using the AWS console Wizards

119
00:05:52.700 --> 00:05:55.500
 to do these but I wanted to show you as we go through each

120
00:05:55.500 --> 00:05:58.100
 of these resources that there is a way to

121
00:05:58.100 --> 00:05:59.600
 create them through the AWS console.

122
00:06:00.400 --> 00:06:03.100
All right. So let's move this route table pane up

123
00:06:03.100 --> 00:06:07.400
 so we can see a little more as you can see here. We got the details card

124
00:06:06.400 --> 00:06:09.700
 that you're used to seeing and

125
00:06:09.700 --> 00:06:12.600
 then the top tabs up here. You have details

126
00:06:12.600 --> 00:06:16.500
 route subnet Association edges route propagation

127
00:06:15.500 --> 00:06:18.400
 and tags. We're only gonna Focus

128
00:06:18.400 --> 00:06:21.300
 here on these first three tabs the details

129
00:06:21.300 --> 00:06:24.300
 routes and subnet associations for this.

130
00:06:24.300 --> 00:06:27.200
 So let's go look on details not much going

131
00:06:27.200 --> 00:06:30.500
 on here except that you have the ID which is rtb -

132
00:06:30.500 --> 00:06:32.400
 the character set they used to seeing

133
00:06:33.300 --> 00:06:36.400
You can see this is associated with the the default

134
00:06:36.400 --> 00:06:39.200
 VPC that Amazon created for

135
00:06:39.200 --> 00:06:41.600
 us. So let's go over and click over on routes.

136
00:06:42.600 --> 00:06:45.400
Okay, so here's the routes and if you remember what we talked about earlier,

137
00:06:45.400 --> 00:06:48.300
 there's a destination and a Target and here we have two

138
00:06:48.300 --> 00:06:51.700
 of them. So our first destination is saying the

139
00:06:51.700 --> 00:06:54.600
 0.0.0.0 / 0 which basically

140
00:06:54.600 --> 00:06:56.500
 means anywhere any IP address?

141
00:06:57.300 --> 00:07:00.500
If Network packet as destined for

142
00:07:00.500 --> 00:07:01.500
 any IP address.

143
00:07:02.600 --> 00:07:05.200
Send it to our internet gateway and we're

144
00:07:05.200 --> 00:07:08.600
 gonna get into it in a Gateway in later video. So I won't go into great

145
00:07:08.600 --> 00:07:11.300
 detail, but here just to know that in a Gateway allows our Linux

146
00:07:11.300 --> 00:07:14.200
 instance to connect to the internet. The second route here

147
00:07:14.200 --> 00:07:17.800
 is the 1723100/16.

148
00:07:18.600 --> 00:07:21.600
And if you recall that is basically the whole IP address

149
00:07:21.600 --> 00:07:23.400
 range of our default VPC.

150
00:07:24.200 --> 00:07:27.600
So what this route is saying to send that to Target with

151
00:07:27.600 --> 00:07:30.700
 this basically means is that any network packet inside

152
00:07:30.700 --> 00:07:33.400
 an ec2 instance for example, and it's

153
00:07:33.400 --> 00:07:36.500
 destined for another IP address inside the

154
00:07:36.500 --> 00:07:38.200
 IP address range.

155
00:07:39.300 --> 00:07:42.900
Then instead of routing that packet anywhere else. This local

156
00:07:42.900 --> 00:07:45.500
 route is just saying keep it local in between

157
00:07:45.500 --> 00:07:47.200
 these instances in this route table.

158
00:07:47.900 --> 00:07:50.300
Obviously, that's it more efficient than trying to send

159
00:07:50.300 --> 00:07:51.700
 it all the way back out and come back in.

160
00:07:52.800 --> 00:07:55.000
Okay, so let's click on subnet associations.

161
00:07:56.100 --> 00:07:59.200
So here we have explicit subnet Association and

162
00:07:59.200 --> 00:08:02.500
 you can see it's empty even though we looked at the subnet it

163
00:08:02.500 --> 00:08:06.100
 said that it was associated with this route and that is because every

164
00:08:05.100 --> 00:08:08.500
 VPC must have a default route and what

165
00:08:08.500 --> 00:08:11.900
 it is is kind of like the fall through so if you create subnets

166
00:08:11.900 --> 00:08:14.800
 and you don't assign it to any route table, then they

167
00:08:14.800 --> 00:08:17.600
 will automatically by default use this

168
00:08:17.600 --> 00:08:20.700
 the default route table to to manage packets.

169
00:08:21.300 --> 00:08:24.700
So by declaration these subnets weren't explicitly set.

170
00:08:24.700 --> 00:08:27.800
 So they just automatically get this route table. And if

171
00:08:27.800 --> 00:08:30.100
 you come down here scroll down to this other card you have

172
00:08:30.100 --> 00:08:33.400
 subnets without explicit expectation. And this is kind of like the pool of

173
00:08:33.400 --> 00:08:37.000
 subnets that you could apply to add dissociation.

174
00:08:36.600 --> 00:08:39.700
 And if you come up here, you can click either

175
00:08:39.700 --> 00:08:42.600
 one of these edit subnet associations, and then

176
00:08:42.600 --> 00:08:45.300
 this will allow you to assign subnets to this route table.

177
00:08:46.500 --> 00:08:49.400
We are obviously not going to do this for the default set because when

178
00:08:49.400 --> 00:08:52.400
 we go to create our lab, we're gonna create our own VPC our own

179
00:08:52.400 --> 00:08:55.900
 route table and our own subnet and we're gonna assign that

180
00:08:55.900 --> 00:08:58.400
 subnet to our own route table, which you'll see

181
00:08:58.400 --> 00:09:00.500
 a little bit more when we get into the terraform file.

182
00:09:01.100 --> 00:09:04.300
All right. Well that pretty much covers what we

183
00:09:04.300 --> 00:09:08.300
 wanted to talk about here in the AWS console for subnets

184
00:09:07.300 --> 00:09:10.400
 and Route tables. So next what we'll

185
00:09:10.400 --> 00:09:13.100
 do let's go jump over into the terminal and then let's look

186
00:09:13.100 --> 00:09:16.300
 at these files these terraform files and what they

187
00:09:16.300 --> 00:09:19.100
 look like and how they're going to create these resources for us.

188
00:09:20.400 --> 00:09:23.700
Okay. So here we are back in the terminal and the

189
00:09:23.700 --> 00:09:26.100
 first file we're gonna look at is subnet and

190
00:09:26.100 --> 00:09:29.900
 so it is subnet dot TF.

191
00:09:29.900 --> 00:09:32.500
 So open that in your favorite editor.

192
00:09:33.500 --> 00:09:36.200
What we're looking at here is what's going to become a staple. Every

193
00:09:36.200 --> 00:09:39.800
 time we open these files is the same kind of layout you

194
00:09:39.800 --> 00:09:42.900
 see the resource declaration. You

195
00:09:42.900 --> 00:09:45.700
 see what type of library or

196
00:09:45.700 --> 00:09:48.300
 what it we're going to use in this case. What type

197
00:09:48.300 --> 00:09:50.600
 of resource and this is the AWS subnet.

198
00:09:51.300 --> 00:09:54.900
And then we named the resource. We name it lab subnet

199
00:09:54.900 --> 00:09:57.800
 public one. And the reason why we named it this resource

200
00:09:57.800 --> 00:10:00.400
 that is because we wanted to kind of match what the actual

201
00:10:00.400 --> 00:10:03.300
 name of the subnets gonna be and this is only just

202
00:10:03.300 --> 00:10:06.200
 for pure preference. You could yeah, I could

203
00:10:06.200 --> 00:10:09.200
 have name this food or Johnny if I wanted to

204
00:10:09.200 --> 00:10:12.300
 and it wouldn't mattered, but I'd like

205
00:10:12.300 --> 00:10:13.900
 to keep them consistent. So it's easy to follow.

206
00:10:14.600 --> 00:10:17.100
Here on line 2 we go ahead and we set

207
00:10:17.100 --> 00:10:20.700
 the VPC ID. Obviously terraform doesn't

208
00:10:20.700 --> 00:10:23.400
 know that yet. It doesn't know until the Tariff until the

209
00:10:23.400 --> 00:10:26.100
 VPC is created. There's an order of operations here that

210
00:10:26.100 --> 00:10:29.000
 terraform works out for us. So that will be

211
00:10:29.500 --> 00:10:33.000
 converted and calculated time here online

212
00:10:32.300 --> 00:10:35.300
 three, we set a cider block. And so

213
00:10:35.300 --> 00:10:38.500
 this cider block here is where if

214
00:10:38.500 --> 00:10:41.400
 you remember the the VPC we're doing the new VPC. Is

215
00:10:41.400 --> 00:10:44.900
 it 10.0.0.0 slash 16 and

216
00:10:44.900 --> 00:10:47.100
 here we're just taking a small slice of that and

217
00:10:47.100 --> 00:10:50.600
 we're saying the 10.0.1 zero, so

218
00:10:50.600 --> 00:10:53.600
 that means any instance that we bring up the subnet

219
00:10:53.600 --> 00:10:57.500
 is going to get a 10.0.1 address slash

220
00:10:56.500 --> 00:10:59.700
 24 just means we will

221
00:10:59.700 --> 00:11:02.400
 only gonna do is 255 hosts that is perfectly

222
00:11:02.400 --> 00:11:06.300
 fine for a like a lab subnet

223
00:11:05.300 --> 00:11:08.100
 where obviously we're not gonna create more than

224
00:11:08.100 --> 00:11:11.600
 255 hosts for this in course

225
00:11:11.600 --> 00:11:13.000
 online for

226
00:11:14.100 --> 00:11:17.200
you can see here with map public IP and launch. So this basically says

227
00:11:17.200 --> 00:11:20.500
 any ec2 instance that ask for a public IP

228
00:11:20.500 --> 00:11:22.300
 address. It's okay to go ahead and assign them one.

229
00:11:23.100 --> 00:11:26.400
Here we're using availability Zone online five. We're just

230
00:11:26.400 --> 00:11:29.600
 setting what the availability Zone and here we're doing the string interpolation

231
00:11:29.600 --> 00:11:31.900
 where we're saying in this variable.

232
00:11:32.700 --> 00:11:35.100
For the variable of AWS region, which happens to

233
00:11:35.100 --> 00:11:38.500
 be Usos 2 were appending a sneaky little a

234
00:11:38.500 --> 00:11:41.400
 down here in the end. Now I'm showing you this one

235
00:11:41.400 --> 00:11:44.000
 way in this file and another file in a later video. I'm going to show you

236
00:11:44.200 --> 00:11:47.300
 another way. I'm just trying to give you I give you some variety of

237
00:11:47.300 --> 00:11:50.300
 what you can do here, but that that is definitely

238
00:11:50.300 --> 00:11:52.200
 just string interpolation way of doing it.

239
00:11:52.900 --> 00:11:55.300
So line seven through nine, we set our

240
00:11:55.300 --> 00:11:58.500
 tags and this is where we're actually naming

241
00:11:58.500 --> 00:12:01.400
 the subnet. So here we're giving it a key of name

242
00:12:01.400 --> 00:12:04.200
 and the value is a lab subnet public

243
00:12:04.200 --> 00:12:07.200
 one as well. Obviously as you can tell here, we're only

244
00:12:07.200 --> 00:12:10.300
 creating one resource in this file. So there's only one subnet and I

245
00:12:10.300 --> 00:12:13.400
 did that just to keep things simple for our lab. We could

246
00:12:13.400 --> 00:12:16.400
 have easily created BC and D as well. And in

247
00:12:16.400 --> 00:12:19.300
 this case you would basically have three more copies of

248
00:12:19.300 --> 00:12:22.700
 lines one through 10 here with different side or

249
00:12:22.700 --> 00:12:25.400
 blocks and obviously a different name. But like I

250
00:12:25.400 --> 00:12:28.100
 said for this course, this is completely fine for one.

251
00:12:28.100 --> 00:12:31.300
 Okay, so let's close this file and then let's go look at our route.

252
00:12:33.400 --> 00:12:36.300
All right, their route file is just route.tf.

253
00:12:37.300 --> 00:12:38.600
So open that up in your editor.

254
00:12:39.600 --> 00:12:42.600
Okay. So here we have two resources in this file to

255
00:12:42.600 --> 00:12:45.300
 discuss and one of them is gonna create the route

256
00:12:45.300 --> 00:12:48.100
 table and the other one is going to associate that subnet that we

257
00:12:48.100 --> 00:12:51.600
 just created or we're looking at creating and Associated that

258
00:12:51.600 --> 00:12:52.400
 with this route table.

259
00:12:53.200 --> 00:12:56.700
So here line two, we got the normal declaration. We're

260
00:12:56.700 --> 00:13:00.000
 going to use the AWS route table resource, and

261
00:12:59.200 --> 00:13:02.600
 we're going to name this resource lab public

262
00:13:02.600 --> 00:13:05.800
 CRT and CRT. Just custom route table.

263
00:13:06.800 --> 00:13:09.800
Line three, we're associating it with our lab VPC

264
00:13:09.800 --> 00:13:12.800
 and still, you know to declare to differentiate

265
00:13:12.800 --> 00:13:13.800
 between that and the default.

266
00:13:14.500 --> 00:13:17.600
Here's our first route if you remember route has a destination and

267
00:13:17.600 --> 00:13:18.100
 a Target.

268
00:13:18.900 --> 00:13:21.200
Destination is the cider block

269
00:13:21.200 --> 00:13:25.200
 saying zero zero zero zero and if

270
00:13:24.200 --> 00:13:27.600
 that comes in go ahead

271
00:13:27.600 --> 00:13:30.500
 and send it to our Gateway and this is the Gateway ID

272
00:13:30.500 --> 00:13:33.900
 that is yet to be shown or created that'll

273
00:13:33.900 --> 00:13:35.500
 be calculated once terraform gets run.

274
00:13:37.100 --> 00:13:40.300
And then here at line lines nine through 11, you can see

275
00:13:40.300 --> 00:13:43.500
 that we're this is our tag our name tag, and this

276
00:13:43.500 --> 00:13:46.100
 is where we're actually naming the route table and here we're calling it

277
00:13:46.100 --> 00:13:48.200
 lab public custom route table.

278
00:13:48.800 --> 00:13:51.600
The sit down the line 15 here. This is the

279
00:13:51.600 --> 00:13:55.000
 resource route table Association. And

280
00:13:54.200 --> 00:13:57.700
 then this one we're just calling it lab custom

281
00:13:57.700 --> 00:14:00.600
 route table Association public subnet one. I

282
00:14:00.600 --> 00:14:03.400
 know not extremely clever, but it does

283
00:14:03.400 --> 00:14:04.200
 tell you what it's doing.

284
00:14:04.800 --> 00:14:07.500
And here we just we basically set a subnet

285
00:14:07.500 --> 00:14:10.300
 ID and a route table ID and that's all you

286
00:14:10.300 --> 00:14:13.300
 need to do. And then once the order of operations is

287
00:14:13.300 --> 00:14:16.400
 a complete where the VPC gets set up the route table and then

288
00:14:16.400 --> 00:14:17.800
 when the subnet is created.

289
00:14:18.500 --> 00:14:21.500
The this resource this Association will then

290
00:14:21.500 --> 00:14:24.300
 be created after that. Once the boat has the route table ID

291
00:14:24.300 --> 00:14:25.400
 and a subnet ID.

292
00:14:26.400 --> 00:14:26.700
Okay.

293
00:14:27.700 --> 00:14:30.300
We are done in this file. So feel free to close that and

294
00:14:30.300 --> 00:14:30.500
 get out.

295
00:14:31.500 --> 00:14:34.200
Let's jump back over and let's do a recap on what we've

296
00:14:34.200 --> 00:14:34.700
 done in this video.

297
00:14:36.100 --> 00:14:39.700
Okay. So in this video you learned about subnets and

298
00:14:39.700 --> 00:14:42.900
 its features like IP addressing cider ranges.

299
00:14:42.900 --> 00:14:45.400
 You also explored route tables in

300
00:14:45.400 --> 00:14:48.900
 a relationship with subnets. You will use both subnets and

301
00:14:48.900 --> 00:14:51.200
 Route tables to allow traffic in and

302
00:14:51.200 --> 00:14:52.200
 out of your Lennox server.

303
00:14:52.800 --> 00:14:55.700
We also navigated to both resources inside

304
00:14:55.700 --> 00:14:58.300
 the AWS console and explored the default

305
00:14:58.300 --> 00:15:00.800
 subnets and Route tables at AWS created for us.

306
00:15:01.600 --> 00:15:04.300
Finally, we looked at the terraform files that would create

307
00:15:04.300 --> 00:15:07.700
 your custom subnet and Route table and the association for

308
00:15:07.700 --> 00:15:08.100
 the lab.

309
00:15:09.700 --> 00:15:12.700
In the next video, we will learn how to filter traffic

310
00:15:12.700 --> 00:15:15.100
 with security groups and connect your Linux server to

311
00:15:15.100 --> 00:15:16.800
 the internet via internet gateway.
