AWS Migration, Disaster Recovery & Well-Architected Framework | AWS CLF-C02 Day 20 — Transcript

Full transcript

1. 0:01Hey, welcome to day 20. We are one day
2. 0:03away from finishing this entire series.
3. 0:05So, let's make today count.
4. 0:07Here's the real world story we are
5. 0:08covering today.
6. 0:10Imagine a company that's been running
7. 0:11its own servers in a basement or a data
8. 0:13center for the last 10 years.
9. 0:16One day, leadership decides we are
10. 0:17moving into AWS.
11. 0:19That decision opens up a bunch of
12. 0:21questions. Like, how do we actually move
13. 0:23everything over?
14. 0:24Do we just copy-paste it or we redesign
15. 0:26it? Once we are in AWS, how do we know
16. 0:29we are building things the right way,
17. 0:31not just a way?
18. 0:32How do we get our whole organization,
19. 0:34not just the tech team, ready for this
20. 0:35shift? What's this actually going to
21. 0:37cost us compared to before? And if
22. 0:39something goes wrong, a server fails, a
23. 0:41whole data center goes down, how fast
24. 0:43can we recover and what's that going to
25. 0:45cost us?
26. 0:46That's exactly the five things we are
27. 0:48covering today. Migration strategy, the
28. 0:50well-architected framework, the cloud
29. 0:52adoption framework, cloud economics, and
30. 0:53disaster recovery. And these all sound
31. 0:56like big separate topics, but they are
32. 0:58really just five chapters of the same
33. 1:00story. A company's journey from we own
34. 1:02everything ourselves to we run
35. 1:04confidently in the cloud. And quick
36. 1:06reassurance before we dive in, none of
37. 1:08this requires you to actually configure
38. 1:10anything. This is 100% a recognition
39. 1:12game for the exam.
40. 1:14You just need to know which term matches
41. 1:16which situation. Here's how today flows.
42. 1:19First, we will cover the strategies
43. 1:20companies use to actually move
44. 1:22application into AWS. There are seven
45. 1:24named approaches, and once you
46. 1:26understand the logic behind them, they
47. 1:28are easy to remember.
48. 1:29Then we will look at the actual AWS tool
49. 1:32that help in migration. Because knowing
50. 1:34the strategy is one thing, but the exam
51. 1:35also wants you to know which specific
52. 1:37tool does which specific job.
53. 1:40After that, we shift into building it
54. 1:41right, the well-architected framework,
55. 1:43which is basically AWS official rulebook
56. 1:46for good cloud architecture.
57. 1:48Right after that, we will cover the
58. 1:49cloud adoption framework, which sounds
59. 1:51similar but is actually about something
60. 1:53completely different. And this mix-up is
61. 1:55one of the most exam common traps, so
62. 1:57pay close attention there.
63. 1:58Then we will recap cloud economics, how
64. 2:00the cloud changes the way companies pay
65. 2:02for technology.
66. 2:03And we will finish with disaster
67. 2:04recovery. This we have covered, I guess,
68. 2:06in previous videos, but we will see that
69. 2:08again. Uh we will see what happens when
70. 2:10things go wrong and how AWS categorizes
71. 2:12the different levels of being prepared.
72. 2:15So, let's get started.
73. 2:16Okay, so picture this. You are moving
74. 2:18apartments. You've got a bunch of stuff
75. 2:20in your old place, and you need to
76. 2:21decide for each item what to do with it.
77. 2:24Some things you will just throw away.
78. 2:26Some things you will leave behind for
79. 2:27now. Some things you will pack exactly
80. 2:29as they are and unpack them the same way
81. 2:30in the new place.
82. 2:32Some things you will fix up a little
83. 2:33during the move. Some things you will
84. 2:34just replace entirely with something
85. 2:36new. And some big furniture you might
86. 2:38completely redesign to fit the new space
87. 2:40better. That's basically what a company
88. 2:42does with each of its application when
89. 2:44moving to AWS. And there's a name for
90. 2:46each of these decisions. AWS calls them
91. 2:48the Rs, because each strategy start with
92. 2:51the letter R. Let's go through all seven
93. 2:54and in order from least effort to the
94. 2:57most effort. We have the first one that
95. 2:59is retire. This is the throw-it-away
96. 3:00option.
97. 3:02The company looks at an old application
98. 3:03and realizes nobody actually uses it
99. 3:05anymore. So, instead of migrating it,
100. 3:07they just shut it down.
101. 3:09Zero migration work, and it's actually
102. 3:10the cheapest option because you are not
103. 3:12paying to move something you don't need.
104. 3:15The next we have is retain. This is
105. 3:16leave it where it is for now. Maybe
106. 3:18there's a compliance reason the data has
107. 3:20to stay on premises, or maybe the
108. 3:21company just bought expensive new
109. 3:23hardware last year, and it doesn't make
110. 3:25financial sense to move that application
111. 3:27yet. So, it stays put, at least
112. 3:29temporarily. The next one is relocate.
113. 3:32And this is the one that's newer and
114. 3:34easy to miss. So, let's be really clear
115. 3:36on it. Relocate means moving the entire
116. 3:39underlying infrastructure to AWS exactly
117. 3:42as it is,
118. 3:43at the virtualization level. A real
119. 3:45example is something called VMware Cloud
120. 3:47on AWS.
121. 3:48Picture an entire set of virtual
122. 3:50machines being picked up as a whole unit
123. 3:52and placed onto the AWS hardware with
124. 3:54literally nothing inside them changing.
125. 3:57The key thing that makes relocate
126. 3:59different from the next one, that is
127. 4:01rehost, is that relocate happens at the
128. 4:03infrastructure or hypervisor level.
129. 4:06The whole environment moves as one block
130. 4:08untouched.
131. 4:10And talking about rehost, often called
132. 4:11the lift and shift, this is moving an
133. 4:14individual application to AWS pretty
134. 4:15much as is with minimal changes.
135. 4:18This is different from relocate because
136. 4:20we are talking about moving an
137. 4:21application over to run on a standard
138. 4:23AWS resources like EC2.
139. 4:26Not shifting an entire virtualized
140. 4:28environment as a block. Rehost is
141. 4:29usually the fastest way to start
142. 4:31migrating because you are not just
143. 4:33redesigning anything. You are just
144. 4:34picking it up and putting it down in a
145. 4:36new location. Now, let's see replatform.
146. 4:39Nicknamed lift, tinker, and shift.
147. 4:42This is rehost's slightly more ambitious
148. 4:44cousin. You move the application over,
149. 4:47but you make a few improvements along
150. 4:49the way. A classic example, instead of
151. 4:51keeping a self-managed database exactly
152. 4:53as it was, you switch it to Amazon RDS
153. 4:55during the move. So, AWS handles the
154. 4:57database maintenance for you going
155. 4:59forward.
156. 5:00The next we have is repurchase. This
157. 5:02means the company decides not to move
158. 5:03the old application at all and instead
159. 5:05switches to a totally different product,
160. 5:08usually a SaaS product.
161. 5:09So, take an example, instead of
162. 5:12continuing to run an old self-built
163. 5:13customer relationship management tool,
164. 5:15the company just switches to a
165. 5:16ready-made cloud CRM product.
166. 5:19So, this is repurchase.
167. 5:20And now talking about refactor or
168. 5:22rearchitect, this is the big one. The
169. 5:25company completely redesigns the
170. 5:26application to be cloud native, built
171. 5:28specifically to take advantage of things
172. 5:30like auto scaling, serverless computing,
173. 5:32or microservices.
174. 5:34This takes the most time and effort of
175. 5:35all seven options, but it also delivers
176. 5:37the most long-term benefit.
177. 5:40Why? Because the application is now
178. 5:42built to fully exploit what the cloud
179. 5:44can do.
180. 5:45Now, here's your exam trap and I want
181. 5:47you to really lock this in. If a
182. 5:49question says fastest way to migrate
183. 5:51with minimal code changes, that's
184. 5:53rehost.
185. 5:54And if it says moving virtual machines
186. 5:56as it using VMware Cloud on AWS, that's
187. 5:59relocate. Don't confuse it with the
188. 6:01rehost because relocate is about the
189. 6:03infrastructure layer moving untouched,
190. 6:05while the rehost is about individual
191. 6:07application moving with minimal changes.
192. 6:10And if the question describes
193. 6:11redesigning for microservices or
194. 6:13serverless, that's refactor.
195. 6:16One more heads-up, you might see this
196. 6:17called the six Rs in some places and the
197. 6:19seven Rs in others, depending on whether
198. 6:21relocate is included. Just know both
199. 6:23terms so neither one throws you off on
200. 6:25the exam day. Now that we know the
201. 6:26strategies, let's talk about the actual
202. 6:28tools AWS gives you to carry them out.
203. 6:31Think of this as strategy is the plan,
204. 6:34tools are the equipment you use to
205. 6:35execute the plan.
206. 6:37The first one we have AWS Migration Hub.
207. 6:40This is your single dashboard, a
208. 6:42bird's-eye view that lets you track the
209. 6:44progress of migration happening across
210. 6:45multiple different AWS and partner
211. 6:47tools, all in one place. Think of it as
212. 6:50mission control.
213. 6:51The next we have AWS Application
214. 6:53Discovery Service. AWS Application
215. 6:55Discovery Service happens before you
216. 6:57migrate anything. Its job is to discover
217. 6:59and catalog what you actually have on
218. 7:00premises, your servers, how they depend
219. 7:03on each other, and how heavily they are
220. 7:04being used. You can't plan a move
221. 7:06properly if you don't know what you are
222. 7:07moving, right? That's what the service
223. 7:09is for.
224. 7:11The next we have AWS Application
225. 7:12Migration Service, often called AWS MGN.
226. 7:15It is the main tool for that rehost
227. 7:17strategy we just talked about, lift and
228. 7:19shift. It continuously replicates your
229. 7:21on-premises servers into AWS, so when
230. 7:23you are ready to cutover, the AWS
231. 7:25version is already up to date.
232. 7:27Next is AWS Database Migration Service,
233. 7:30or AWS DMS.
234. 7:32It moves database into AWS with minimal
235. 7:34downtime. And here's something powerful
236. 7:36about it, it can migrate between
237. 7:38different database engine, not just the
238. 7:39same one.
239. 7:41Then we have AWS schema conversion tool
240. 7:44or AWS SCT. It works alongside DBS, but
241. 7:47it does something different. It converts
242. 7:49the database schema, meaning the
243. 7:50structure and the design of the database
244. 7:52from one engine to another. Think of
245. 7:54migrating from Oracle to Aurora
246. 7:56PostgreSQL. Those two database don't
247. 7:58structure things the same way
248. 7:59internally. So, SCT translate that
249. 8:01structure before DMS moves the actual
250. 8:02data.
251. 8:03And finally, a quick recap of the AWS
252. 8:05Snow family, the physical devices AWS
253. 8:07ships you for migrating extremely large
254. 8:10offline data sets for situations where
255. 8:12transferring the data over the internet
256. 8:13would simply take too long.
257. 8:16And here's your exam prep for this
258. 8:17slide, and it's a big one.
259. 8:19DMS moves the data. What was DMS?
260. 8:22Database Migration Service.
261. 8:24And SCT converts the schema. SCT was
262. 8:26Schema Conversion Tool.
263. 8:28If you are migrating between the same
264. 8:30database engine, say MySQL to MySQL, you
265. 8:32only need DMS because there is no
266. 8:34structural translation needed. SCT only
267. 8:37comes into play when you are switching
268. 8:38between different types of databases.
269. 8:40All right, here's a really important
270. 8:42concept, so let's build it up properly.
271. 8:44Imagine AWS has been watching thousands
272. 8:46and thousands of companies build things
273. 8:48in the cloud for over a decade.
274. 8:50Some of those companies built things
275. 8:51really well, reliable, secure,
276. 8:53cost-effective systems.
277. 8:55Others built things poorly and ran into
278. 8:57problems. AWS took everything they
279. 8:59learned from watching both the good
280. 9:00examples and the bad examples, and they
281. 9:02packaged it into an official framework,
282. 9:04a rule book essentially for how to build
283. 9:07good cloud architecture. And that rule
284. 9:09book is called AWS Well-Architected
285. 9:11Framework, and it's built around six
286. 9:13pillars. Let's go through each one, and
287. 9:15I want you to notice that each pillar is
288. 9:17really answering just a different
289. 9:18question about your system.
290. 9:20Operational excellence answers the
291. 9:21question, how do we run and monitor the
292. 9:23system and keep improving? How do we
293. 9:25operate it over time? This is about your
294. 9:28day-to-day processes.
295. 9:29And security answers, how do we protect
296. 9:31our data, our systems, and our assets?
297. 9:34This involves assessing risk and putting
298. 9:36the right protection in place.
299. 9:38And we have reliability. This answers,
300. 9:41can this system recover if something
301. 9:42fails? And can it consistently handle
302. 9:45the demand placed on it? This is about
303. 9:47resilience.
304. 9:48And we have performance efficiency. It
305. 9:50answers, are we using our computing
306. 9:52resources efficiently? And are we
307. 9:54adapting as our needs and available
308. 9:56technology change over time?
309. 9:59Another we have cost optimization. It
310. 10:01answers, are we avoiding unnecessary
311. 10:03spending and are we getting the best
312. 10:04value for what we do spend?
313. 10:06This is cost optimization.
314. 10:09And sustainability, this is the newest
315. 10:10pillar. It is added because it matters
316. 10:13more and more.
317. 10:14Answers,
318. 10:15are we minimizing the environmental
319. 10:17impacts of the workloads we are running?
320. 10:20A simple memory trick for these six,
321. 10:22OSRPCS.
322. 10:24OSRPCS.
323. 10:27Operational excellence, security,
324. 10:29reliability, performance efficiency,
325. 10:31cost optimization, sustainability.
326. 10:34Say that a few times and it sticks.
327. 10:36OSRPCS.
328. 10:39AWS also gives you something called the
329. 10:40AWS Well-Architected Tool, a free tool
330. 10:43inside the console that actually reviews
331. 10:45your specific workloads against these
332. 10:47six pillars and gives you a real
333. 10:49recommendation on where you are falling
334. 10:51short.
335. 10:52For the exam, expect questions that
336. 10:54describe a situation and ask you which
337. 10:56pillar it relates to.
338. 10:58For example, if a scenario talks about a
339. 10:59company reducing its carbon footprint,
340. 11:01that's sustainability.
341. 11:03If it talks about making sure our
342. 11:05systems survive a server crash without
343. 11:07going down, that is reliability.
344. 11:10All right, so now here's where I need
345. 11:12you to pay a very close attention
346. 11:14because this is one of the single most
347. 11:16commonly confused pairs on the whole
348. 11:17exam.
349. 11:18Well-Architected Framework versus Cloud
350. 11:20Adoption Framework. They sound almost
351. 11:22identical, but they solve completely
352. 11:24different problems. Well-Architected
353. 11:26Framework, which we just covered, is
354. 11:27about how to build a workload
355. 11:29technically. It's for engineers thinking
356. 11:31about a specific system.
357. 11:33The Cloud Adoption Framework or AWS CAF
358. 11:36is about something much bigger.
359. 11:39It's about how an entire organization
360. 11:41plans and executes its overall journey
361. 11:43into the cloud.
362. 11:44This isn't about any one technical
363. 11:46system. It's about people, processes,
364. 11:48culture, and strategy.
365. 11:50Think about it this way. A company
366. 11:52moving to the cloud isn't just a
367. 11:54technology change. It's an
368. 11:55organizational change. Employees need
369. 11:57new skills, processes need to be
370. 11:59rethought, leadership needs a plan. CAF
371. 12:02exists to guide all of that.
372. 12:05CAF organizes this transformation into
373. 12:06six perspective, and they split nearly
374. 12:08into two groups.
375. 12:10The first group is business-facing
376. 12:11perspectives.
377. 12:13Business is making sure that cloud
378. 12:16investments actually accelerate real
379. 12:18business outcome, not just technology
380. 12:19for technology's sake.
381. 12:21People evolving the skill, culture, and
382. 12:24organizational structure of the company,
383. 12:26so people are actually ready for this
384. 12:28shift.
385. 12:29Governance is aligning IT strategy with
386. 12:31business goals and properly managing
387. 12:33risk along the way.
388. 12:36That is the first group, uh
389. 12:37business-facing perspective. The second
390. 12:40group is technical perspective.
391. 12:42We have platform, the technical
392. 12:44foundation for actually building
393. 12:45workloads.
394. 12:47Security, securing that technical
395. 12:49foundation, and operations is running
396. 12:51and operating those workloads
397. 12:52day-to-day.
398. 12:54And here's something worth knowing for
399. 12:55the exam. AWS CAF isn't just a process.
400. 12:59It's meant to deliver real, measurable
401. 13:01business benefits. Specifically, reduced
402. 13:04business risk, improved environmental,
403. 13:05social, and governance performance,
404. 13:07often shortened to ESG, increased
405. 13:09revenue, and increased operational
406. 13:10efficiency.
407. 13:12If you see an exam question asking,
408. 13:13"What's the benefit of using AWS CAF?"
409. 13:15Those four outcomes are exactly what
410. 13:18it's pointing at.
411. 13:20So, here's your memory anchor for the
412. 13:21exam trap. Well-Architected Framework is
413. 13:24equal to how to build a workload
414. 13:26technically.
415. 13:27And CAF is equal to how an organization
416. 13:29plans its overall move to the cloud. One
417. 13:32is technical and specific, the other is
418. 13:34organizational and broad. Don't let the
419. 13:36similar names trick you.
420. 13:39Now, let's talk about money.
421. 13:41Specifically, how financial model of the
422. 13:43cloud is fundamentally different from
423. 13:44owning your own hardware.
424. 13:46When a company runs its own data center,
425. 13:48it has fixed costs. Meaning, it has to
426. 13:50spend a large amount of money up front
427. 13:52to buy servers and hardwares, regardless
428. 13:55of how much they actually get used
429. 13:56afterward. This is called CAPEX, short
430. 13:59for capital expenditure.
431. 14:01You're paying big money before you even
432. 14:02know how much you will actually need it.
433. 14:05But in the cloud, instead, you have
434. 14:06variable costs. You only pay what you
435. 14:09actually use with no upfront hardware
436. 14:11purchase required at all. This is called
437. 14:13OPEX, short for operational expenditure.
438. 14:16It is completely different financial
439. 14:18mindset. Pay as you go, instead of pay
440. 14:20upfront and hope.
441. 14:22All right? So, now let's talk about
442. 14:24licensing, because companies often
443. 14:26already own software licenses from
444. 14:28before they move to the cloud.
445. 14:30And AWS gives them options here.
446. 14:33Bring your own license or BYOL means the
447. 14:35company uses a software license it
448. 14:36already owns and runs that software on
449. 14:38AWS infrastructure. The other option is
450. 14:41included license, where AWS bundles the
451. 14:43license cost right into what you pay
452. 14:45them. So, you don't have to manage your
453. 14:47own license separately. Here's an
454. 14:49important nuance for the exam.
455. 14:51BYOL can be cheaper, especially if the
456. 14:53company already owns the license and
457. 14:55doesn't want to pay for it twice.
458. 14:58And but and this is the trap. BYOL
459. 15:00requires the company to track its own
460. 15:02license compliance. AWS does not manage
461. 15:05that for you. Remember that. So, BYOL
462. 15:09can save money, but it shifts
463. 15:10responsibility onto the customer.
464. 15:13Next, resizing. That means matching the
465. 15:14size of your AWS resources to what you
466. 15:17actually need, instead of over
467. 15:18provisioning just in case.
468. 15:20AWS has a tool called compute optimizer
469. 15:23that automatically analyze your usage
470. 15:24and recommends the right size for you
471. 15:26based on the real data instead of
472. 15:28guesswork.
473. 15:29And finally, economics of scale. Because
474. 15:32AWS serves millions of customer across
475. 15:34the entire world, their sheer purchasing
476. 15:36power lets them buy hardware and
477. 15:38infrastructure at massive scale that
478. 15:40drives down the cost per unit. And
479. 15:43here's a key part, AWS passes a lot of
480. 15:45those saving down to customers over
481. 15:46time. Which is part of why cloud pricing
482. 15:49tends to get cheaper as AWS grows larger
483. 15:51and not more expensive. Okay, last big
484. 15:54topic for today and this one is
485. 15:55genuinely fun once it clicks because
486. 15:57it's really just a spectrum of how much
487. 15:59are you willing to pay to sleep well at
488. 16:00night.
489. 16:02Let's start with two terms you
490. 16:02absolutely must understand because the
491. 16:04exam loves testing the difference
492. 16:06between them and we might have studied
493. 16:08this on the previous lectures as well.
494. 16:10The first one is RTO, that is recovery
495. 16:12time objective. It is about time,
496. 16:15especially it's the maximum amount of
497. 16:17time your system is allowed to be
498. 16:19completely down after disaster before it
499. 16:21becomes unacceptable.
500. 16:23Think of it as how long can we survive
501. 16:25being offline?
502. 16:27The next we have RPO, that is recovery
503. 16:29point objective. It is about data.
504. 16:32It's the maximum amount of data loss you
505. 16:34can tolerate measured in time. Meaning
506. 16:36how far can your last good backup be?
507. 16:39Think of it as how much recent work are
508. 16:41we willing to lose?
509. 16:43All right. So here's the fundamental
510. 16:45rule that ties this whole topic
511. 16:46together. The lower your RTO and RPO,
512. 16:49meaning the less down time and the less
513. 16:50data loss you can tolerate. And the more
514. 16:53expensive and complex your disaster
515. 16:55recovery setup needs to be.
516. 16:57There's a direct relationship between
517. 16:58how fast and complete your recovery is
518. 17:01and how much it costs to maintain that
519. 17:02readiness.
520. 17:03AWS defines four disaster recovery
521. 17:06strategies and they form a ladder from
522. 17:07cheapest and slowest to most expensive
523. 17:10and fastest.
524. 17:11Backup and restore is the cheapest
525. 17:12option. You simply store your backups in
526. 17:14S3 and Glacier and if the disaster
527. 17:16strike, you can restore everything from
528. 17:18scratch because you are literally
529. 17:20rebuilding from zero. This takes the
530. 17:22longest and your RTO here is measured in
531. 17:24hours to days.
532. 17:26And pilot light is the next step up.
533. 17:28Imagine a pilot light on a gas stove.
534. 17:30It's this tiny flame that's always
535. 17:32burning ready to ignite the rest of the
536. 17:34stove instantly. In AWS terms, this
537. 17:37means you keep your core database always
538. 17:39running in a secondary region. While
539. 17:41everything else, your application
540. 17:43servers and so on, stays switched off
541. 17:45until you actually need them. When
542. 17:46disaster hits, you turn the rest on
543. 17:48quickly. RTO here drops to tens of
544. 17:50minutes. We have warm standby. It goes
545. 17:53further. You keep a scale down and fully
546. 17:55functional version of your entire
547. 17:56environment running continuously in a
548. 17:58secondary region. It's a smaller than
549. 18:00your full production setup, but it's
550. 18:02alive and working the whole time. So,
551. 18:03when disaster strikes, you just scale it
552. 18:05up rather than starting it from nothing.
553. 18:07RTO drops to just minutes.
554. 18:10And finally, multi-site active.
555. 18:12The most expensive option. Your full
556. 18:14production environment runs
557. 18:15simultaneously in two or more regions at
558. 18:17the same time. Both actively serving
559. 18:20traffic. If one region goes down, the
560. 18:22other is already running and takes over
561. 18:24instantly. This gets you RTO that's near
562. 18:26zero, but obviously running two full
563. 18:28production environments cost
564. 18:29significantly more than any of the other
565. 18:31options. Here's your exam trap and this
566. 18:33is a classic scenario matching question.
567. 18:35RTO of 1 day and we want to minimize
568. 18:38cost. It points to backup and restore.
569. 18:42RTO of minutes and some added cost is
570. 18:45acceptable. It points to warm standby.
571. 18:48We have near zero RTO because this is
572. 18:50mission critical. It points to
573. 18:52multi-site active or active. The exam
574. 18:54will describe a business need and you
575. 18:56need to match it to the right point on
576. 18:58this cost versus speed ladder. Okay, so
577. 19:01now let's bring it all together. The
578. 19:03seven R's of migration from least to
579. 19:06most effort. Retire, retain, relocate,
580. 19:10rehost, replatform, repurchase, and
581. 19:13refactor. Remember, relocate moves
582. 19:15infrastructure as is at the hypervisor
583. 19:17level with zero application changes.
584. 19:19That's what separates it from rehost.
585. 19:22For migration tools, DMS migration data,
586. 19:24SCT convert schema, migration hub tracks
587. 19:28progress across tools, and application
588. 19:30discovery service handles the planning
589. 19:32phase before you even start moving
590. 19:34anything.
591. 19:36We have well-architected framework. It
592. 19:37gives you six pillars for building a
593. 19:39technically sound workload. Remember
594. 19:41OSRPCs we discussed about? CAF gives you
595. 19:45six perspective for building an entire
596. 19:47organization cloud adoption journey,
597. 19:49delivering reduced risk and better EC2
598. 19:51performance, increased revenue, and
599. 19:52increased efficiency.
600. 19:54Different tools, different scope, so
601. 19:56don't mix them up.
602. 19:58RTO is your maximum acceptable downtime,
603. 19:59and RPO is your maximum acceptable data
604. 20:02loss. And disaster recovery strategy
605. 20:04scales from backup and restore, the
606. 20:06cheapest and slowest, all the way to the
607. 20:08multi-site active or active the most
608. 20:10expensive and fastest. So, for tonight,
609. 20:13go back through today's five topics and
610. 20:15make sure you can explain each exam trap
611. 20:17out loud in your own words without
612. 20:19looking at your notes. All right? And
613. 20:21also, do the assessment which is given
614. 20:22for today.
615. 20:23If you can do that, you have genuinely
616. 20:25got this material.
617. 20:27Tomorrow is day 21, our final channel
618. 20:29day. We are covering storage, backup,
619. 20:31business application, billing support,
620. 20:34and the AWS partner ecosystem.
621. 20:36See you there for the finish line. Have
622. 20:38a great day ahead.