WEBVTT

1
00:00.000 --> 00:03.120
Now just like there are three different types of cloud infrastructures, we're

2
00:03.120 --> 00:04.000
going to be looking at

3
00:04.000 --> 00:08.400
three different types of service models that those cloud infrastructures can

4
00:08.400 --> 00:09.840
use. Perutations.

5
00:09.840 --> 00:14.440
Sorry, the math nerd may stick it out, but we're going to be taking a look at

6
00:14.440 --> 00:16.000
software as a service,

7
00:16.000 --> 00:19.920
platform as a service, and infrastructure as a service to kind of tie

8
00:19.920 --> 00:21.520
everything up altogether

9
00:21.520 --> 00:25.780
and how they work between the public, private, and hybrid or community cloud

10
00:25.780 --> 00:27.040
infrastructures.

11
00:27.040 --> 00:30.560
And if we take a look at software as a service first, this is software
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

11
00:27.040 --> 00:30.560
And if we take a look at software as a service first, this is software

12
00:30.560 --> 00:32.160
applications delivered

13
00:32.160 --> 00:36.660
over the internet and it accessed usually through a web browser. Think of this

14
00:36.660 --> 00:37.360
as like office

15
00:37.360 --> 00:42.990
365 or Gmail or something along those lines. Easily accessible from home over a

16
00:42.990 --> 00:43.840
web browser

17
00:43.840 --> 00:50.800
and over the internet and usually works very well with a public based cloud

18
00:50.800 --> 00:51.440
infrastructure

19
00:51.440 --> 00:55.640
environment because you can access it nearly anywhere in the world. It's a

20
00:55.640 --> 00:56.240
little bit more

21
00:56.240 --> 01:00.220
difficult on the private side because it's a private infrastructure and as we
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

21
00:56.240 --> 01:00.220
difficult on the private side because it's a private infrastructure and as we

22
01:00.220 --> 01:00.880
talked about

23
01:00.880 --> 01:05.690
earlier when we were going over private cloud environments, you would need some

24
01:05.690 --> 01:06.960
sort of dedicated

25
01:06.960 --> 01:11.430
communication link between point A and point B to be able to get inside of that

26
01:11.430 --> 01:12.320
private cloud.

27
01:12.320 --> 01:17.190
And then in hybrid, you would be connecting to the public side and then travers

28
01:17.190 --> 01:18.000
ing through

29
01:18.000 --> 01:21.560
those dedicated links to be able to get to the hybrid or community

30
01:21.560 --> 01:22.720
infrastructure.

31
01:23.360 --> 01:27.950
But this allows us the software as a service allows us to be able to manage

32
01:27.950 --> 01:28.960
user accounts,

33
01:28.960 --> 01:33.820
the secure application data, and it's your proper configuration of service
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

33
01:28.960 --> 01:33.820
the secure application data, and it's your proper configuration of service

34
01:33.820 --> 01:34.720
settings

35
01:34.720 --> 01:38.400
on the service side of the house, basically where we're configured everything

36
01:38.400 --> 01:39.040
behind the scenes

37
01:39.040 --> 01:44.000
in that cloud environment to make sure that services like office 365 are

38
01:44.000 --> 01:46.240
accessible and through

39
01:46.240 --> 01:53.200
user permissions available to those users. So keep them within that CAH Triad

40
01:53.200 --> 02:00.160
Confidentiality Integrity and Availability. And this isn't just limited to SMTP
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

40
01:53.200 --> 02:00.160
Confidentiality Integrity and Availability. And this isn't just limited to SMTP

41
02:00.160 --> 02:01.760
or email.

42
02:01.760 --> 02:06.400
It's also for things like the Google workspace and whatever else may be out

43
02:06.400 --> 02:07.600
there. So you could

44
02:07.600 --> 02:12.830
definitely set this up as a AWS if you want to use that third party service out

45
02:12.830 --> 02:14.320
there or Microsoft

46
02:14.320 --> 02:20.080
Azure and set up an environment where users can conduct transactions or be able

47
02:20.080 --> 02:20.880
to view different

48
02:20.880 --> 02:26.100
products or conduct shared workspaces over that software as a service because

49
02:26.100 --> 02:26.960
we're not actually

50
02:26.960 --> 02:32.140
dealing with the program or operating system or anything on the end user side.
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

50
02:26.960 --> 02:32.140
dealing with the program or operating system or anything on the end user side.

51
02:32.140 --> 02:32.880
It's just making it

52
02:32.880 --> 02:37.160
as easy and available as possible. This moves us on to platform as a service

53
02:37.160 --> 02:38.160
and you may notice a

54
02:38.160 --> 02:42.760
trending theme here of we're getting nidier and grittier closer to the actual

55
02:42.760 --> 02:43.920
barebone systems.

56
02:43.920 --> 02:49.140
See, platform as a service offers us a platform to be able to develop, run, and

57
02:49.140 --> 02:50.240
manage applications

58
02:50.240 --> 02:54.160
without having to deal with things like operating systems or security patches.

59
02:54.160 --> 02:56.480
And this is

60
02:56.480 --> 03:00.800
primarily done commercially available to the public over the internet as well,
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

60
02:56.480 --> 03:00.800
primarily done commercially available to the public over the internet as well,

61
03:00.800 --> 03:01.200
but we're not

62
03:01.200 --> 03:05.730
using the web browser. We're using things like Google app engine, Microsoft

63
03:05.730 --> 03:07.200
Azure app services,

64
03:07.200 --> 03:11.710
and whatever the case may be to be able to help us develop those programs that

65
03:11.710 --> 03:12.880
run as a software

66
03:12.880 --> 03:17.450
as a service environment for those users connecting through generally a web

67
03:17.450 --> 03:19.120
browser. But using platform

68
03:19.120 --> 03:23.330
as a service allows us to protect our application code from users on the

69
03:23.330 --> 03:24.960
outside and manage access

70
03:24.960 --> 03:29.640
controls and secure the development and deployment of those different

71
03:29.640 --> 03:31.440
environments inside of that
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

71
03:29.640 --> 03:31.440
environments inside of that

72
03:31.440 --> 03:37.040
platform. So we're able to develop different applications that are accessible

73
03:37.040 --> 03:38.000
as a software as a

74
03:38.000 --> 03:42.070
service without releasing the code or making the program available to the

75
03:42.070 --> 03:43.840
general public. It's housed

76
03:43.840 --> 03:49.280
in a cloud environment and is accessible through those different resources. Now

77
03:49.280 --> 03:51.040
, I mentioned resources

78
03:51.040 --> 03:55.950
because we need to be able to move on and allocate more memory, more services

79
03:55.950 --> 03:57.520
are excuse me, more

80
03:57.520 --> 04:01.890
processing, more storage, just in case the app that we develop that runs as a
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

80
03:57.520 --> 04:01.890
processing, more storage, just in case the app that we develop that runs as a

81
04:01.890 --> 04:03.600
platform as a service

82
04:03.600 --> 04:07.940
gets overburdened allows us to be able to on the fly add more resources and

83
04:07.940 --> 04:09.920
that's moving down into

84
04:09.920 --> 04:14.640
infrastructure as a service. Now, once we get into infrastructure as a service,

85
04:14.640 --> 04:15.360
we're talking about

86
04:15.360 --> 04:20.370
providing virtualized computing resources that very same memories, same storage

87
04:20.370 --> 04:21.360
and same processing

88
04:21.360 --> 04:25.580
power. We just mentioned that we may need for our platform that runs our

89
04:25.580 --> 04:27.200
software. See, Daisy

90
04:27.200 --> 04:31.630
Chained along and all that great stuff. But we're basically taking a virtual
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

90
04:27.200 --> 04:31.630
Chained along and all that great stuff. But we're basically taking a virtual

91
04:31.630 --> 04:32.880
ized environment and

92
04:32.880 --> 04:38.570
making it accessible to those on the internet. So in terms of being able to

93
04:38.570 --> 04:39.360
access that

94
04:39.360 --> 04:43.830
infrastructure, this will be something like ESXi inside the VMWare world or

95
04:43.830 --> 04:46.240
going down to the nuts and

96
04:46.240 --> 04:51.030
bolts of Amazon Web Service and Microsoft Azure virtual machines like Hyper-V

97
04:51.030 --> 04:52.720
platform type stuff

98
04:52.720 --> 04:56.800
and being able to go through and allocate said resources, issue out those

99
04:56.800 --> 04:57.840
virtual machines that

100
04:57.840 --> 05:03.890
will run that platform or run that service or server to run that service. And
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

100
04:57.840 --> 05:03.890
will run that platform or run that service or server to run that service. And

101
05:03.890 --> 05:05.120
this allows us to be

102
05:05.120 --> 05:09.700
able to get more detailed on that actual security because we're at the virtual

103
05:09.700 --> 05:11.040
machine slash operating

104
05:11.040 --> 05:16.540
system level and we can manage the network security that is within that virtual

105
05:16.540 --> 05:17.600
ized environment.

106
05:17.600 --> 05:24.480
Just in case we want to be able to limit, let's say apply a access control list

107
05:24.480 --> 05:26.320
or a web application,

108
05:26.320 --> 05:30.670
firewall and protect data stored within side of that cloud environment, whether
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

108
05:26.320 --> 05:30.670
firewall and protect data stored within side of that cloud environment, whether

109
05:30.670 --> 05:31.680
it be a public

110
05:31.680 --> 05:37.500
private or hybrid slash community cloud. And infrastructure as a service is

111
05:37.500 --> 05:39.920
generally going to be at a

112
05:39.920 --> 05:45.120
very bare bone, just about as bare bone as you can get level when it comes to

113
05:45.120 --> 05:46.000
working with things

114
05:46.000 --> 05:50.800
on the cloud because you're going to need to access directly to those systems

115
05:50.800 --> 05:52.400
to be able to install

116
05:52.400 --> 05:57.960
virtual machines or modify said virtual machines. Now it could be that you are

117
05:57.960 --> 05:58.720
in some sort of

118
05:58.720 --> 06:03.840
environment to where you are allocated, you log in through ESXi or through the
WEBVTT
X-TIMESTAMP-MAP=LOCAL:00:00:00.000,MPEGTS:900000

118
05:58.720 --> 06:03.840
environment to where you are allocated, you log in through ESXi or through the

119
06:03.840 --> 06:05.440
Azure virtual

120
06:05.440 --> 06:09.850
machine management console and you go in and you're allowed to play within a

121
06:09.850 --> 06:10.960
certain resource

122
06:10.960 --> 06:15.280
pool that's already pre-allocated to you. But you're actually working on those

123
06:15.280 --> 06:16.480
physical systems

124
06:16.480 --> 06:20.030
that are all tied together inside of that cloud environment to be able to build

125
06:20.030 --> 06:21.120
out that platform

126
06:21.120 --> 06:22.560
as a service.