WEBVTT
Kind: captions
Language: en

1
00:00:00.000 --> 00:00:07.427
Our store's team now knows how to build well on AWS. But moving a whole company to the cloud takes

2
00:00:07.427 --> 00:00:14.778
more than good architecture. This lesson covers task 1.3 in Domain 1, migration to the AWS Cloud,

3
00:00:14.778 --> 00:00:20.159
plus the database migration tools from Domain 3. We'll cover two ideas.

4
00:00:20.159 --> 00:00:26.979
First, the AWS Cloud Adoption Framework, its six perspectives and the outcomes it targets.

5
00:00:26.979 --> 00:00:33.800
Second, the seven migration strategies, called the 7 Rs, and the tools that do the moving.

6
00:00:34.200 --> 00:00:41.054
The AWS Cloud Adoption Framework, or CAF, is AWS guidance for moving a whole organization to the

7
00:00:41.054 --> 00:00:46.194
cloud. The Well-Architected Framework asks: is this workload built well?

8
00:00:46.194 --> 00:00:52.620
The CAF asks a bigger question: is our organization ready? It covers people and processes,

9
00:00:52.620 --> 00:00:58.046
not just servers and code. AWS suggests an iterative journey in four phases:

10
00:00:58.046 --> 00:01:03.900
envision the value, align teams and close gaps, launch pilots, then scale them up.

11
00:01:04.300 --> 00:01:09.142
The CAF groups its guidance into six perspectives, each with its own stakeholders.

12
00:01:09.142 --> 00:01:14.869
Three focus on business capabilities. The business perspective makes sure cloud investments drive

13
00:01:14.869 --> 00:01:20.714
business outcomes; think chief executive and chief financial officer. The people perspective covers

14
00:01:20.714 --> 00:01:26.264
culture, leadership, skills and change management. And the governance perspective orchestrates

15
00:01:26.264 --> 00:01:31.932
cloud initiatives, maximizing benefits while limiting risk, so it involves people like the chief

16
00:01:31.932 --> 00:01:32.732
risk officer.

17
00:01:33.100 --> 00:01:38.872
The other three perspectives focus on technical capabilities. The platform perspective helps you

18
00:01:38.872 --> 00:01:44.523
build a scalable, hybrid cloud platform and modernize workloads; architects and engineers live

19
00:01:44.523 --> 00:01:50.235
here. The security perspective protects the confidentiality, integrity and availability of data

20
00:01:50.235 --> 00:01:56.127
and workloads, led by the chief information security officer. And the operations perspective makes

21
00:01:56.127 --> 00:02:02.199
sure cloud services run at the level the business needs, with operations leaders and site reliability

22
00:02:02.199 --> 00:02:02.999
engineers.

23
00:02:03.200 --> 00:02:08.258
Why use the CAF? The exam guide names four business outcomes. Reduced business risk,

24
00:02:08.258 --> 00:02:14.219
through better reliability and security. Improved environmental, social and governance performance,

25
00:02:14.219 --> 00:02:18.495
or ESG, for example by running on more energy-efficient infrastructure.

26
00:02:18.495 --> 00:02:23.071
Increased revenue, because new products and features reach customers faster.

27
00:02:23.071 --> 00:02:27.587
And increased operational efficiency, with less time spent running servers.

28
00:02:27.587 --> 00:02:31.200
For our store, that means fewer outages and faster launches.

29
00:02:31.600 --> 00:02:37.437
Once you're ready, every application needs a migration strategy. AWS lists seven,

30
00:02:37.437 --> 00:02:44.283
known as the 7 Rs. Retire means switching off what nobody needs, like the store's old fax-order

31
00:02:44.283 --> 00:02:51.201
system. Retain means keeping it where it is for now, maybe because it depends on local hardware.

32
00:02:51.201 --> 00:02:56.317
Rehost, or lift and shift, moves an application as is, with no changes.

33
00:02:56.317 --> 00:03:03.091
Relocate moves a whole platform, such as VMware virtual machines, to its cloud version without

34
00:03:03.091 --> 00:03:04.100
changing them.

35
00:03:04.500 --> 00:03:09.502
The last three involve more change. Repurchase, also called drop and shop,

36
00:03:09.502 --> 00:03:14.841
replaces the application with a different product, often software as a service.

37
00:03:14.841 --> 00:03:21.195
Replatform, or lift, tinker and shift, adds a few cloud optimizations, like moving the store's

38
00:03:21.195 --> 00:03:26.129
database to Amazon RDS so AWS handles patching and backups. And refactor,

39
00:03:26.129 --> 00:03:31.604
or re-architect, redesigns the app with cloud-native features such as serverless.

40
00:03:31.604 --> 00:03:36.200
It's the most work, so teams often rehost first and modernize later.

41
00:03:36.600 --> 00:03:42.645
AWS has tools for each step. To assess, AWS Application Discovery Service finds your servers,

42
00:03:42.645 --> 00:03:48.820
their usage and dependencies, and Migration Evaluator builds a business case with projected AWS

43
00:03:48.820 --> 00:03:54.995
costs. To move, AWS Application Migration Service rehosts servers; it's now named AWS Transform

44
00:03:54.995 --> 00:04:00.845
MGN. AWS Database Migration Service moves databases, and AWS DataSync copies files online.

45
00:04:00.845 --> 00:04:06.955
Migration Hub, Application Discovery Service and Snowball Edge no longer accept new customers,

46
00:04:06.955 --> 00:04:09.100
but the exam can still name them.

47
00:04:09.500 --> 00:04:16.482
The exam guide's migration example is database replication. Say the store moves its database to

48
00:04:16.482 --> 00:04:21.700
Amazon RDS. AWS DMS first copies the existing data, called a full load.

49
00:04:21.700 --> 00:04:28.683
Then ongoing replication copies each new change, so the source stays online and the store keeps

50
00:04:28.683 --> 00:04:34.342
taking orders. When the copy is in sync, you cut over. If the engines differ,

51
00:04:34.342 --> 00:04:41.177
say Oracle to PostgreSQL, first convert the schema with the AWS Schema Conversion Tool or DMS

52
00:04:41.177 --> 00:04:42.500
Schema Conversion.

53
00:04:42.900 --> 00:04:48.889
Here's how the exam asks about this. Moving an application as is, with no changes,

54
00:04:48.889 --> 00:04:54.220
is rehost. Moving to a managed database with a few changes is replatform.

55
00:04:54.220 --> 00:05:01.597
Replacing an application with a SaaS product is repurchase. Redesigning it with cloud-native features

56
00:05:01.597 --> 00:05:08.462
is refactor. Keeping a database in sync during a migration is AWS DMS, and converting a schema

57
00:05:08.462 --> 00:05:15.400
to a different engine is AWS SCT. Staff skills and culture point to the CAF people perspective.

58
00:05:15.800 --> 00:05:21.457
To recap: the Cloud Adoption Framework prepares a whole organization for the cloud.

59
00:05:21.457 --> 00:05:26.773
Its six perspectives are business, people and governance on the business side,

60
00:05:26.773 --> 00:05:32.429
and platform, security and operations on the technical side. It targets lower risk,

61
00:05:32.429 --> 00:05:38.768
better ESG performance, more revenue and more efficiency. The 7 Rs run from retire and retain

62
00:05:38.768 --> 00:05:44.697
to refactor, and DMS with SCT moves databases. Next, we'll see where AWS actually runs:

63
00:05:44.697 --> 00:05:47.900
Regions, Availability Zones and edge locations.
