WEBVTT
Kind: captions
Language: en

1
00:00:00.000 --> 00:00:06.442
So far we've looked at why the cloud saves money and how to keep the bill low.

2
00:00:06.442 --> 00:00:12.470
Now we'll look at how to build well on AWS. This is task 1.2 in Domain 1:

3
00:00:12.470 --> 00:00:21.472
design principles of the AWS Cloud. We'll cover two ideas. First, the six pillars of the AWS Well-Architected

4
00:00:21.472 --> 00:00:29.483
Framework. Second, how to tell the pillars apart on the exam, and the free tool that reviews your

5
00:00:29.483 --> 00:00:31.300
workload against them.

6
00:00:31.700 --> 00:00:37.778
AWS compares building a system to constructing a building: if the foundation isn't solid,

7
00:00:37.778 --> 00:00:44.676
problems show up later. The Well-Architected Framework gives you best practices and design principles

8
00:00:44.676 --> 00:00:50.002
in six areas, called pillars, and questions to review a workload against them.

9
00:00:50.002 --> 00:00:55.876
It also helps you weigh trade-offs between pillars. But it's guidance, not automation:

10
00:00:55.876 --> 00:00:59.700
it shows you the risks, and your team makes the changes.

11
00:01:00.100 --> 00:01:05.914
The first pillar is operational excellence: running workloads well, seeing how they behave,

12
00:01:05.914 --> 00:01:11.984
and continuously improving the way you operate. Its design principles include safely automating

13
00:01:11.984 --> 00:01:17.416
operations as code, making frequent, small, reversible changes, anticipating failure,

14
00:01:17.416 --> 00:01:23.358
for example with practice events called game days, and learning from every operational event.

15
00:01:23.358 --> 00:01:29.300
Our store ships small updates from a template, so a bad change can be rolled back in minutes.

16
00:01:29.700 --> 00:01:34.721
The second pillar is security: using cloud technologies to protect data,

17
00:01:34.721 --> 00:01:41.694
systems and assets. Its design principles include a strong identity foundation with least privilege,

18
00:01:41.694 --> 00:01:48.458
so each person gets only the access they need. Traceability, so every action and change is logged

19
00:01:48.458 --> 00:01:53.479
and audited. Security at every layer, from the network edge to the code.

20
00:01:53.479 --> 00:01:58.500
And protecting data in transit and at rest, for example with encryption.

21
00:01:58.900 --> 00:02:04.806
The third pillar is reliability: a workload doing its job correctly and consistently when it's

22
00:02:04.806 --> 00:02:10.712
expected to, and recovering when something breaks. Its design principles include automatically

23
00:02:10.712 --> 00:02:16.744
recovering from failure, testing your recovery procedures, scaling horizontally by replacing one

24
00:02:16.744 --> 00:02:21.205
large resource with several small ones, and stopping guessing capacity.

25
00:02:21.205 --> 00:02:27.300
If one of the store's web servers fails, a healthy server takes over and customers keep shopping.

26
00:02:27.700 --> 00:02:33.591
The fourth pillar is performance efficiency: using computing resources efficiently to meet your

27
00:02:33.591 --> 00:02:38.366
requirements, and staying efficient as demand changes and technology evolves.

28
00:02:38.366 --> 00:02:43.202
Its design principles include using advanced technologies as managed services,

29
00:02:43.202 --> 00:02:48.039
going global in minutes with multiple Regions, using serverless architectures,

30
00:02:48.039 --> 00:02:53.992
and experimenting more often. The store's team can test two instance types side by side and keep

31
00:02:53.992 --> 00:02:56.100
the one that serves pages fastest.

32
00:02:56.500 --> 00:03:02.534
The fifth pillar is cost optimization: delivering business value at the lowest price point.

33
00:03:02.534 --> 00:03:08.700
Its design principles include adopting a consumption model, so you pay only for what you use,

34
00:03:08.700 --> 00:03:15.330
measuring overall efficiency, stopping spending money on undifferentiated heavy lifting like running

35
00:03:15.330 --> 00:03:21.497
data centers, and analyzing and attributing spending. That's what lessons three and four were

36
00:03:21.497 --> 00:03:27.000
about: the store stops test servers at night, and tags show which team spends what.

37
00:03:27.400 --> 00:03:33.652
The sixth pillar, sustainability, is the newest: AWS added it in 2021. It's about reducing the

38
00:03:33.652 --> 00:03:39.771
environmental impact of a workload, using less energy and fewer resources for the same work.

39
00:03:39.771 --> 00:03:44.692
Its design principles include understanding your impact and setting goals,

40
00:03:44.692 --> 00:03:51.210
maximizing utilization, using managed services, and adopting more efficient hardware and software.

41
00:03:51.210 --> 00:03:55.400
One busy server uses less energy than two that sit mostly idle.

42
00:03:55.800 --> 00:04:02.213
Two pairs of pillars cause most mistakes. Reliability asks: does it keep working and recover after

43
00:04:02.213 --> 00:04:08.429
a failure? Performance efficiency asks: is this the right resource, and is it used efficiently?

44
00:04:08.429 --> 00:04:14.776
A failed server being replaced is reliability; switching to a faster resource type is performance

45
00:04:14.776 --> 00:04:21.123
efficiency. Cost optimization is about money wasted. Sustainability is about energy and resources

46
00:04:21.123 --> 00:04:25.900
used. Consolidating idle servers helps both, so read the question's goal.

47
00:04:26.300 --> 00:04:32.869
To review a real workload, use the AWS Well-Architected Tool in the AWS Management Console,

48
00:04:32.869 --> 00:04:39.654
at no charge. You define a workload, such as the store's web app, and answer questions grouped

49
00:04:39.654 --> 00:04:46.655
by pillar. The tool shows high and medium risks and builds an improvement plan you can track with

50
00:04:46.655 --> 00:04:53.368
milestones. The Well-Architected Framework lens is always applied, and you can add lenses for

51
00:04:53.368 --> 00:04:56.400
areas like serverless or machine learning.

52
00:04:56.800 --> 00:05:01.825
Here's how the exam asks about this. Recovering automatically from failure is reliability.

53
00:05:01.825 --> 00:05:05.845
Using resources efficiently as demand changes is performance efficiency.

54
00:05:05.845 --> 00:05:09.809
Running, monitoring and improving operations is operational excellence.

55
00:05:09.809 --> 00:05:15.002
Least privilege, traceability and encryption point to security. Avoiding unnecessary costs is

56
00:05:15.002 --> 00:05:19.078
cost optimization, and minimizing environmental impact is sustainability.

57
00:05:19.078 --> 00:05:23.600
And reviewing a workload against best practices is the AWS Well-Architected Tool.

58
00:05:24.000 --> 00:05:29.656
To recap: the Well-Architected Framework has six pillars. Operational excellence runs and improves

59
00:05:29.656 --> 00:05:35.370
operations. Security protects data and systems. Reliability recovers from failure and meets demand.

60
00:05:35.370 --> 00:05:40.968
Performance efficiency uses the right resources efficiently. Cost optimization avoids unnecessary

61
00:05:40.968 --> 00:05:46.682
cost, and sustainability reduces environmental impact. The Well-Architected Tool reviews a workload

62
00:05:46.682 --> 00:05:52.223
against them at no charge. Next, we'll see how companies plan their move with the Cloud Adoption

63
00:05:52.223 --> 00:05:53.023
Framework.
