1
00:00:00,000 --> 00:00:01,680
Once your organization has determined

2
00:00:01,680 --> 00:00:04,140
that using the cloud is the right solution for them,

3
00:00:04,140 --> 00:00:05,837
the next decision is whether to host it onsite

4
00:00:05,837 --> 00:00:10,470
or to contract it as a hosted solution from a third party.

5
00:00:10,470 --> 00:00:12,270
When hosting a solution onsite,

6
00:00:12,270 --> 00:00:14,940
this is often referred to as on-premise.

7
00:00:14,940 --> 00:00:16,440
While using on-premise solutions

8
00:00:16,440 --> 00:00:18,330
are great from a security standpoint,

9
00:00:18,330 --> 00:00:19,605
they are extremely costly,

10
00:00:19,605 --> 00:00:22,110
and you're going to have to have an entire team of people

11
00:00:22,110 --> 00:00:24,390
working to support those solutions.

12
00:00:24,390 --> 00:00:26,198
Now, if you decide to use an on-premise solution,

13
00:00:26,198 --> 00:00:29,130
that means you're going to need to procure all the hardware,

14
00:00:29,130 --> 00:00:31,590
the software, and all the personnel necessary,

15
00:00:31,590 --> 00:00:34,170
to run your organization's cloud solution.

16
00:00:34,170 --> 00:00:35,340
In addition to this,

17
00:00:35,340 --> 00:00:36,900
you're also going to need to have a facility

18
00:00:36,900 --> 00:00:38,040
for that data center,

19
00:00:38,040 --> 00:00:39,390
which can hold all the equipment

20
00:00:39,390 --> 00:00:41,340
and provide adequate space, power,

21
00:00:41,340 --> 00:00:43,860
and cooling for it to work properly.

22
00:00:43,860 --> 00:00:46,680
Because of this, many organizations instead decide

23
00:00:46,680 --> 00:00:48,390
to use a hosted solution.

24
00:00:48,390 --> 00:00:49,770
With a hosted environment,

25
00:00:49,770 --> 00:00:51,270
a third party service provider

26
00:00:51,270 --> 00:00:54,000
is going to provide you with all the hardware and facilities

27
00:00:54,000 --> 00:00:56,190
needed to maintain your cloud solution.

28
00:00:56,190 --> 00:00:58,920
This is often done in a multi-tenancy environment

29
00:00:58,920 --> 00:01:00,270
with multiple organizations

30
00:01:00,270 --> 00:01:01,830
having their cloud solutions hosted

31
00:01:01,830 --> 00:01:04,769
within a single third party provider's facility.

32
00:01:04,769 --> 00:01:07,800
For example, Amazon, Microsoft, and Google,

33
00:01:07,800 --> 00:01:11,160
all provide hosted solutions for organizations to utilize.

34
00:01:11,160 --> 00:01:15,150
Consider the example of Amazon Web Services, or AWS.

35
00:01:15,150 --> 00:01:16,283
This multi-tenancy solution

36
00:01:16,283 --> 00:01:18,810
utilizes the same physical hardware,

37
00:01:18,810 --> 00:01:21,000
located at the same physical facility,

38
00:01:21,000 --> 00:01:24,150
to support a large number of diverse organizations.

39
00:01:24,150 --> 00:01:26,640
Of course, there are logical separations in place

40
00:01:26,640 --> 00:01:27,960
to keep your data secure,

41
00:01:27,960 --> 00:01:29,940
and from being exposed to other organizations

42
00:01:29,940 --> 00:01:31,650
within the hosted platform.

43
00:01:31,650 --> 00:01:33,300
But if you have information

44
00:01:33,300 --> 00:01:35,520
that you want to remain strictly confidential,

45
00:01:35,520 --> 00:01:38,460
you are much better off using an on-premise solution

46
00:01:38,460 --> 00:01:40,694
where you can control all the physical and logical access

47
00:01:40,694 --> 00:01:42,690
to those servers.

48
00:01:42,690 --> 00:01:44,760
When using a multi-tenancy solution,

49
00:01:44,760 --> 00:01:45,967
residual data from your organization

50
00:01:45,967 --> 00:01:48,300
may be exposed to another tenant,

51
00:01:48,300 --> 00:01:51,600
as the server elasticity expands upward or downward

52
00:01:51,600 --> 00:01:54,540
to provision and deprovision excess server capacity,

53
00:01:54,540 --> 00:01:56,760
since you're utilizing the same shared resources

54
00:01:56,760 --> 00:01:58,440
as everybody else.

55
00:01:58,440 --> 00:02:00,540
If you decide to use a hosting provider,

56
00:02:00,540 --> 00:02:01,980
it's really important to understand

57
00:02:01,980 --> 00:02:04,530
their authentication and authorization mechanisms

58
00:02:04,530 --> 00:02:06,810
to ensure that they have adequate protections in place

59
00:02:06,810 --> 00:02:08,490
to meet your requirements.

60
00:02:08,490 --> 00:02:10,556
Also, you should inquire about the redundancy

61
00:02:10,556 --> 00:02:12,360
and fault tolerance measures

62
00:02:12,360 --> 00:02:13,770
to ensure that they're up to the level

63
00:02:13,770 --> 00:02:15,420
that you're going to require.

64
00:02:15,420 --> 00:02:18,570
Another concern with hosted providers is their location.

65
00:02:18,570 --> 00:02:21,570
Where exactly is your data going to be stored in the world?

66
00:02:21,570 --> 00:02:22,890
Based on that location,

67
00:02:22,890 --> 00:02:25,860
what laws are going to affect your organization and its data?

68
00:02:25,860 --> 00:02:27,210
These are things you have to understand

69
00:02:27,210 --> 00:02:29,070
when choosing a hosted service provider

70
00:02:29,070 --> 00:02:31,110
for your organization.

71
00:02:31,110 --> 00:02:32,220
Now that you've made the decision

72
00:02:32,220 --> 00:02:33,840
on whether or not to use an on-premise

73
00:02:33,840 --> 00:02:35,370
or hosted service provider,

74
00:02:35,370 --> 00:02:37,170
the last decision is going to revolve around

75
00:02:37,170 --> 00:02:39,780
what type of service you want to purchase.

76
00:02:39,780 --> 00:02:42,180
Now, there are three main cloud service models

77
00:02:42,180 --> 00:02:43,170
to choose from.

78
00:02:43,170 --> 00:02:45,720
These are software as a service, or SaaS,

79
00:02:45,720 --> 00:02:47,730
platform as a service, or PaaS,

80
00:02:47,730 --> 00:02:50,400
and infrastructure as a service, or IaaS.

81
00:02:50,400 --> 00:02:52,290
Now under software as a service,

82
00:02:52,290 --> 00:02:54,390
the service provider is going to give your organization

83
00:02:54,390 --> 00:02:56,040
a complete solution.

84
00:02:56,040 --> 00:02:57,240
This includes the hardware,

85
00:02:57,240 --> 00:02:58,830
such as networking, storage,

86
00:02:58,830 --> 00:03:00,540
servers and virtualization,

87
00:03:00,540 --> 00:03:01,890
as well as the operating system,

88
00:03:01,890 --> 00:03:03,630
the middleware, the runtime,

89
00:03:03,630 --> 00:03:04,800
the data processing,

90
00:03:04,800 --> 00:03:06,480
and the application or software

91
00:03:06,480 --> 00:03:07,470
that's needed for the service

92
00:03:07,470 --> 00:03:09,360
to be delivered to your end user.

93
00:03:09,360 --> 00:03:12,720
For example, if your organization is using Office 365

94
00:03:12,720 --> 00:03:16,200
from Microsoft, or Docs and Sheets by Google Workspace,

95
00:03:16,200 --> 00:03:18,900
these are considered a software as a service solution,

96
00:03:18,900 --> 00:03:21,450
and it allows your end users to access their email,

97
00:03:21,450 --> 00:03:23,070
their documents, their spreadsheets,

98
00:03:23,070 --> 00:03:26,220
and more, all directly within their web browser.

99
00:03:26,220 --> 00:03:28,230
Another good example of software as a service

100
00:03:28,230 --> 00:03:30,810
is TurboTax and QuickBooks Online.

101
00:03:30,810 --> 00:03:33,510
These provide tax filing and bookkeeping software

102
00:03:33,510 --> 00:03:36,240
that you can access online using just your web browser,

103
00:03:36,240 --> 00:03:37,680
and they're going to handle all the software,

104
00:03:37,680 --> 00:03:39,990
all the hardware, and all the data storage requirements,

105
00:03:39,990 --> 00:03:41,430
on your behalf.

106
00:03:41,430 --> 00:03:43,410
Sometimes though, you're going to have to build

107
00:03:43,410 --> 00:03:45,660
a customized application or piece of software

108
00:03:45,660 --> 00:03:47,790
to meet your specific service needs.

109
00:03:47,790 --> 00:03:50,310
In this case, you might only need the service provider

110
00:03:50,310 --> 00:03:51,510
to give you the hardware,

111
00:03:51,510 --> 00:03:53,340
including the networking, storage,

112
00:03:53,340 --> 00:03:55,080
servers and virtualization,

113
00:03:55,080 --> 00:03:56,550
as well as the operating system,

114
00:03:56,550 --> 00:03:58,860
middleware, and runtime applications.

115
00:03:58,860 --> 00:04:01,560
But, unlike a software as a service solution,

116
00:04:01,560 --> 00:04:03,030
you're going to be responsible for creating

117
00:04:03,030 --> 00:04:04,590
the actual application code

118
00:04:04,590 --> 00:04:06,210
and handling the data processing

119
00:04:06,210 --> 00:04:08,550
between your client and your servers.

120
00:04:08,550 --> 00:04:10,170
Now, with platform as a service,

121
00:04:10,170 --> 00:04:12,300
you're going to get the benefits of using the cloud,

122
00:04:12,300 --> 00:04:15,180
including shared resources, metered utilization,

123
00:04:15,180 --> 00:04:17,730
rapid elasticity, high availability,

124
00:04:17,730 --> 00:04:19,320
and file synchronization.

125
00:04:19,320 --> 00:04:20,970
But you also have the ability

126
00:04:20,970 --> 00:04:22,590
to customize your own development

127
00:04:22,590 --> 00:04:24,600
to meet your business needs.

128
00:04:24,600 --> 00:04:26,670
Under this model, the third party vendor

129
00:04:26,670 --> 00:04:28,140
is going to provide your organization

130
00:04:28,140 --> 00:04:30,510
with the hardware and operating system software

131
00:04:30,510 --> 00:04:32,820
that's needed for a specific service to operate,

132
00:04:32,820 --> 00:04:35,730
but they're not going to give you the code or the application

133
00:04:35,730 --> 00:04:37,710
that is closest to the end user.

134
00:04:37,710 --> 00:04:39,810
For example, if your company is developing

135
00:04:39,810 --> 00:04:41,310
a new web application,

136
00:04:41,310 --> 00:04:42,840
they might have a development platform

137
00:04:42,840 --> 00:04:45,390
that's provided by a third party cloud provider.

138
00:04:45,390 --> 00:04:47,280
At my company, Dion Training,

139
00:04:47,280 --> 00:04:48,510
as we're filming this,

140
00:04:48,510 --> 00:04:49,620
we're actually in the process

141
00:04:49,620 --> 00:04:51,720
of developing our own learning management system

142
00:04:51,720 --> 00:04:53,130
from the ground up,

143
00:04:53,130 --> 00:04:54,690
but we don't want to have to deal with

144
00:04:54,690 --> 00:04:56,820
all the underlying hardware, networking,

145
00:04:56,820 --> 00:04:59,100
storage, and operating system layers.

146
00:04:59,100 --> 00:05:01,800
So we chose platform as a service

147
00:05:01,800 --> 00:05:04,290
as our solution through Amazon Web Services,

148
00:05:04,290 --> 00:05:05,730
because they're going to handle everything

149
00:05:05,730 --> 00:05:08,220
from the database downward in our tech stack.

150
00:05:08,220 --> 00:05:10,170
And my team and I are only responsible

151
00:05:10,170 --> 00:05:12,480
for the software code that our end users,

152
00:05:12,480 --> 00:05:14,490
our students, are going to interact with,

153
00:05:14,490 --> 00:05:15,840
and then processing the data

154
00:05:15,840 --> 00:05:18,090
as our students go through our courses.

155
00:05:18,090 --> 00:05:20,550
Now, this is platform as a service at work,

156
00:05:20,550 --> 00:05:22,560
because Amazon is giving us the servers,

157
00:05:22,560 --> 00:05:24,180
the operating system configurations,

158
00:05:24,180 --> 00:05:25,710
and even the databases,

159
00:05:25,710 --> 00:05:27,150
and then we're able to build

160
00:05:27,150 --> 00:05:28,830
whatever we want on top of them,

161
00:05:28,830 --> 00:05:31,170
to provide our final application or software

162
00:05:31,170 --> 00:05:33,870
to our end users, which is our students.

163
00:05:33,870 --> 00:05:36,420
The final type of cloud service model we need to cover

164
00:05:36,420 --> 00:05:39,960
is known as IaaS, or infrastructure as a service.

165
00:05:39,960 --> 00:05:41,550
Now, infrastructure as a service

166
00:05:41,550 --> 00:05:43,830
is a means of provisioning IT resources,

167
00:05:43,830 --> 00:05:45,690
such as servers, load balancers,

168
00:05:45,690 --> 00:05:48,570
and storage area network components, when needed.

169
00:05:48,570 --> 00:05:50,340
With infrastructure as a service,

170
00:05:50,340 --> 00:05:51,390
you're going to get the benefits

171
00:05:51,390 --> 00:05:53,640
of dynamic allocation of additional resources,

172
00:05:53,640 --> 00:05:55,470
which is known as elasticity,

173
00:05:55,470 --> 00:05:57,420
but you don't have to deal with the headache

174
00:05:57,420 --> 00:05:58,560
of a long-term commitment

175
00:05:58,560 --> 00:06:01,500
of buying and running all of that hardware yourself.

176
00:06:01,500 --> 00:06:03,272
For example, you might contract for a new

177
00:06:03,272 --> 00:06:07,230
cloud-based web server to host your company's website on.

178
00:06:07,230 --> 00:06:10,380
If you're using Amazon Web Services, or AWS,

179
00:06:10,380 --> 00:06:12,240
we would call this EC2,

180
00:06:12,240 --> 00:06:14,310
which is the elastic cloud compute,

181
00:06:14,310 --> 00:06:15,143
and you're going to be able to select

182
00:06:15,143 --> 00:06:18,300
the right amount of resources for your EC2 instance.

183
00:06:18,300 --> 00:06:19,650
Maybe you decided you wanted four CPUs,

184
00:06:19,650 --> 00:06:23,430
16 gigabytes of memory, 500 gigabytes of storage,

185
00:06:23,430 --> 00:06:24,780
or whatever it is.

186
00:06:24,780 --> 00:06:27,630
Then AWS is going to assign those hardware resources

187
00:06:27,630 --> 00:06:28,620
to you to use,

188
00:06:28,620 --> 00:06:30,360
and you can then install the operating system,

189
00:06:30,360 --> 00:06:33,360
the middleware, and the runtime to that resource.

190
00:06:33,360 --> 00:06:36,720
Now, sometimes the lines can get a bit blurry, though.

191
00:06:36,720 --> 00:06:38,381
According to the official CompTIA textbook

192
00:06:38,381 --> 00:06:40,080
and documentation,

193
00:06:40,080 --> 00:06:43,350
infrastructure as a service is focused on the hardware only,

194
00:06:43,350 --> 00:06:45,330
including the virtual machines, storage,

195
00:06:45,330 --> 00:06:47,880
and networking portions of that hardware.

196
00:06:47,880 --> 00:06:50,160
That being said though, most providers,

197
00:06:50,160 --> 00:06:52,170
like Amazon, Microsoft Azure,

198
00:06:52,170 --> 00:06:53,340
and Google Cloud,

199
00:06:53,340 --> 00:06:55,140
will have you select the operating system

200
00:06:55,140 --> 00:06:57,660
you want to have installed on your compute instance

201
00:06:57,660 --> 00:06:59,580
when you choose what resources you want,

202
00:06:59,580 --> 00:07:01,410
and they're going to assign them to you.

203
00:07:01,410 --> 00:07:03,539
For example, Amazon's EC2 instances

204
00:07:03,539 --> 00:07:05,610
can be spun up automatically

205
00:07:05,610 --> 00:07:08,640
with the Linux Amazon machine image already installed,

206
00:07:08,640 --> 00:07:11,010
and this contains the basic Linux operating system,

207
00:07:11,010 --> 00:07:14,220
ready for you to completely customize to meet your needs.

208
00:07:14,220 --> 00:07:15,360
The reason I bring this up

209
00:07:15,360 --> 00:07:16,800
is because when you're dealing with something

210
00:07:16,800 --> 00:07:18,420
that is mostly hardware,

211
00:07:18,420 --> 00:07:20,730
just because it has the operating system installed,

212
00:07:20,730 --> 00:07:23,114
I would not consider that to be a platform as a service

213
00:07:23,114 --> 00:07:24,854
on the exam, and instead,

214
00:07:24,854 --> 00:07:28,260
you would still choose infrastructure as a service.

215
00:07:28,260 --> 00:07:30,570
Now, to get to the platform as a service level,

216
00:07:30,570 --> 00:07:32,580
it really should include all of the middleware

217
00:07:32,580 --> 00:07:34,020
and the runtime as well.

218
00:07:34,020 --> 00:07:36,300
This includes things like the database functionality,

219
00:07:36,300 --> 00:07:38,910
the web server, such as Apache or Nginx,

220
00:07:38,910 --> 00:07:40,890
and other server software and middleware

221
00:07:40,890 --> 00:07:43,830
that you're going to need to be able to provide those services.

222
00:07:43,830 --> 00:07:46,140
Now for the exam, they're usually going to be pretty clear

223
00:07:46,140 --> 00:07:48,150
when something is infrastructure as a service

224
00:07:48,150 --> 00:07:49,680
or software as a service,

225
00:07:49,680 --> 00:07:51,570
but for platform as a service,

226
00:07:51,570 --> 00:07:53,220
it can be a bit trickier.

227
00:07:53,220 --> 00:07:55,284
So I'm going to give you a little bit of a hint here

228
00:07:55,284 --> 00:07:57,750
that you should use on the exam.

229
00:07:57,750 --> 00:07:59,040
If you see things that are

230
00:07:59,040 --> 00:08:01,350
more than infrastructure as a service,

231
00:08:01,350 --> 00:08:03,630
you probably want to choose platform as a service

232
00:08:03,630 --> 00:08:04,800
as your answer.

233
00:08:04,800 --> 00:08:07,950
If you see things that are less than software as a service,

234
00:08:07,950 --> 00:08:10,650
you would then again choose platform as a service,

235
00:08:10,650 --> 00:08:12,810
because really you have the two ends of the spectrum,

236
00:08:12,810 --> 00:08:14,100
with infrastructure as a service

237
00:08:14,100 --> 00:08:15,420
all the way on the left side,

238
00:08:15,420 --> 00:08:17,580
and software as a service, all the way on the right,

239
00:08:17,580 --> 00:08:20,280
and platform as a service somewhere in the middle.

240
00:08:20,280 --> 00:08:22,860
So in summary, for infrastructure as a service,

241
00:08:22,860 --> 00:08:25,260
remember, it provides you with everything you need

242
00:08:25,260 --> 00:08:26,460
to run a server.

243
00:08:26,460 --> 00:08:28,950
This includes power, space, cooling,

244
00:08:28,950 --> 00:08:30,600
the network, firewalls,

245
00:08:30,600 --> 00:08:32,549
physical servers, the virtualization layer,

246
00:08:32,549 --> 00:08:35,130
and sometimes the operating system.

247
00:08:35,130 --> 00:08:36,166
Now with platform as a service,

248
00:08:36,166 --> 00:08:38,309
we're going to add in the operating system,

249
00:08:38,309 --> 00:08:41,610
and what I like to refer to as the infrastructure software.

250
00:08:41,610 --> 00:08:42,960
Now, this infrastructure software

251
00:08:42,960 --> 00:08:45,480
is really your middleware and runtime environment,

252
00:08:45,480 --> 00:08:47,130
and that means we're talking about things like

253
00:08:47,130 --> 00:08:49,950
an Apache web server, a MySQL database,

254
00:08:49,950 --> 00:08:52,440
programming languages, and things like that.

255
00:08:52,440 --> 00:08:54,390
Now, when we deal with software as a service,

256
00:08:54,390 --> 00:08:57,180
we're dealing with a hosted application piece of software

257
00:08:57,180 --> 00:08:59,010
that's added on top of the infrastructure

258
00:08:59,010 --> 00:09:01,380
and platform portions we just discussed.

259
00:09:01,380 --> 00:09:02,610
So as you can see,

260
00:09:02,610 --> 00:09:05,400
software as a service is much closer to your end user

261
00:09:05,400 --> 00:09:06,632
than either platform as a service

262
00:09:06,632 --> 00:09:09,090
or infrastructure as a service.

263
00:09:09,090 --> 00:09:10,357
So as an IT professional,

264
00:09:10,357 --> 00:09:12,810
it's really important that you're able to determine

265
00:09:12,810 --> 00:09:14,760
which type of "as a service"

266
00:09:14,760 --> 00:09:15,923
is right for your organization,

267
00:09:15,923 --> 00:09:17,670
based on its requirements.

268
00:09:17,670 --> 00:09:19,140
And that's what we covered in this lesson,

269
00:09:19,140 --> 00:09:20,790
talking about software as a service,

270
00:09:20,790 --> 00:09:23,540
platform as a service, and infrastructure as a service.

