WEBVTT
Kind: captions
Language: en

1
00:00:00.000 --> 00:00:06.101
Welcome to lesson four. We start objective 1.3: cloud concepts and connectivity options.

2
00:00:06.101 --> 00:00:12.618
In lesson three our small office built its own network. Now the company moves its online store

3
00:00:12.618 --> 00:00:18.303
into a public cloud. We'll look at three things. Network functions virtualization,

4
00:00:18.303 --> 00:00:24.959
which turns network gear into software. The virtual private cloud, the private network you build

5
00:00:24.959 --> 00:00:31.545
inside a provider's cloud. And the gateways and security rules that decide what traffic gets in

6
00:00:31.545 --> 00:00:32.345
and out.

7
00:00:32.500 --> 00:00:39.248
First, network functions virtualization, or NFV. Traditionally, every network job needed its own

8
00:00:39.248 --> 00:00:45.292
box: a router, a firewall, a load balancer. With NFV, those functions run as software,

9
00:00:45.292 --> 00:00:50.986
called virtual network functions or VNFs, on standard servers under a hypervisor.

10
00:00:50.986 --> 00:00:56.609
You can deploy a new firewall in minutes, or add more copies when traffic grows.

11
00:00:56.609 --> 00:01:03.286
Cloud providers rely on this idea: the routers, firewalls and gateways you use in the cloud are

12
00:01:03.286 --> 00:01:04.200
all software.

13
00:01:04.600 --> 00:01:12.132
Next, the virtual private cloud, or VPC. It's a logically isolated network inside a public cloud,

14
00:01:12.132 --> 00:01:17.645
just for your account. You choose its private IP range as a CIDR block,

15
00:01:17.645 --> 00:01:24.944
here 10.0.0.0/16, and split it into subnets. Our store puts its web server in a public subnet,

16
00:01:24.944 --> 00:01:32.708
and its app server and database in a private subnet. Route tables decide where each subnet's traffic

17
00:01:32.708 --> 00:01:37.600
goes. Azure calls this a VNet, and Oracle Cloud calls it a VCN.

18
00:01:38.000 --> 00:01:44.420
How do customers reach the web server? Through an internet gateway, attached to the VPC.

19
00:01:44.420 --> 00:01:51.205
It's a two-way door between the VPC and the internet. What makes a subnet public is its route

20
00:01:51.205 --> 00:01:58.062
table: a default route, 0.0.0.0/0, pointing to the internet gateway. The web server also needs

21
00:01:58.062 --> 00:02:05.066
a public IP address. In AWS, the gateway translates between that public address and the server's

22
00:02:05.066 --> 00:02:10.100
private one. Outsiders can start connections in, so we'll need rules.

23
00:02:10.500 --> 00:02:16.824
The app server and database live in the private subnet. They have no public addresses,

24
00:02:16.824 --> 00:02:23.735
and nobody on the internet should reach them. But the app server still needs software updates.

25
00:02:23.735 --> 00:02:30.721
That's the job of a NAT gateway. It sits in the public subnet, and the private subnet's default

26
00:02:30.721 --> 00:02:36.897
route points to it. Private instances can start connections out and get the replies,

27
00:02:36.897 --> 00:02:43.000
sharing the gateway's public address. But the internet can't start a connection in.

28
00:02:43.400 --> 00:02:50.227
Now the rules. A network security group is a set of firewall rules attached to chosen instances,

29
00:02:50.227 --> 00:02:56.912
through their network interfaces. Our web server's group allows HTTPS on port 443 from anyone,

30
00:02:56.912 --> 00:03:02.957
and SSH only from the admin's address. In AWS, security groups have allow rules only,

31
00:03:02.957 --> 00:03:08.646
so everything else is denied. They're also stateful: if a request is allowed in,

32
00:03:08.646 --> 00:03:15.900
the reply is allowed out automatically. Azure's network security groups add deny rules and priorities.

33
00:03:16.300 --> 00:03:23.616
A network security list works at the subnet level instead: its rules apply to every instance in

34
00:03:23.616 --> 00:03:31.241
the subnet. That's the name Oracle Cloud uses. In AWS, the equivalent is the network access control

35
00:03:31.241 --> 00:03:38.865
list, or network ACL. An AWS network ACL has allow and deny rules, checked in order from the lowest

36
00:03:38.865 --> 00:03:45.334
number, and the first match wins. It's stateless, so you must allow the replies too.

37
00:03:45.334 --> 00:03:48.800
It's a useful second layer behind the groups.

38
00:03:49.200 --> 00:03:55.476
Let's compare them side by side. A security group protects the instances you choose,

39
00:03:55.476 --> 00:04:02.424
while a security list or network ACL covers a whole subnet. In AWS, groups allow only and are

40
00:04:02.424 --> 00:04:09.522
stateful, while network ACLs can allow or deny, are stateless, and are checked in number order.

41
00:04:09.522 --> 00:04:15.872
A packet from the internet passes the subnet's list first, then the instance's group.

42
00:04:15.872 --> 00:04:21.700
Using both gives you defense in depth, so one mistake doesn't expose a server.

43
00:04:22.100 --> 00:04:29.343
On the exam, match the clue to the answer. Routers and firewalls running as virtual machines on

44
00:04:29.343 --> 00:04:35.748
standard servers means NFV. A logically isolated network in a public cloud is a VPC.

45
00:04:35.748 --> 00:04:43.144
Two-way internet access for a subnet is an internet gateway. A private subnet that needs outbound

46
00:04:43.144 --> 00:04:49.930
updates only is a NAT gateway. Rules attached to specific instances are a security group,

47
00:04:49.930 --> 00:04:54.200
and rules for a whole subnet are a security list or ACL.

48
00:04:54.600 --> 00:05:01.415
To recap: NFV runs network functions as software on standard servers. A VPC is your isolated network

49
00:05:01.415 --> 00:05:07.754
in the cloud, split into subnets with route tables. An internet gateway gives a public subnet

50
00:05:07.754 --> 00:05:14.092
two-way internet access, while a NAT gateway lets private instances reach out without letting

51
00:05:14.092 --> 00:05:20.362
anyone in. Security groups protect chosen instances, and security lists cover whole subnets.

52
00:05:20.362 --> 00:05:26.700
Next, we'll connect the cloud to the office, and compare cloud deployment and service models.
