Six advantages
AWS names six benefits, and the exam quotes them
The six advantages of cloud computing are the stock answers of domain 1. Learn them as worded.
AWS has an official list of six advantages of cloud computing, and exam questions use its wording. Trade fixed expense for variable expense: pay as you use, not before. Benefit from massive economies of scale. Stop guessing capacity. Increase speed and agility. Stop spending money running and maintaining data centres. Go global in minutes. A question describes a situation, and you choose the advantage that answers that situation, not just one that is true.
Six advantages · Going deeper
Eight words the options are built from
Elastic means it shrinks as well as grows. Highly available means it survives a failure.
Elasticity
Capacity that follows demand removes the idle part of the bill
Sized for the peak, this fixed capacity sits about 54% idle. Elastic capacity does not.
Here is why elasticity matters, in one day of a shop's traffic. A data centre has to be sized for the busiest hour, the red line, and it costs the same all day. The shaded area is capacity that is paid for and idle: about 54 percent of it in this example. The purple line is the real demand. On AWS, capacity follows that line, up for the evening peak and back down afterwards.
Check yourself
A ticket site is overwhelmed for ten minutes whenever a concert goes on sale, and quiet otherwise. Which benefit answers this?
Well-Architected Framework
Six pillars, each asking one question of a workload
Know the six pillars by name and by the question each asks.
The Well-Architected Framework is how AWS judges whether a workload is built well. It has six pillars. Operational excellence: can we run it and improve it? Security: is it protected? Reliability: does it keep working and recover? Performance efficiency: are we using the right resources? Cost optimization: are we paying only for value? Sustainability: how little can it consume? Exam questions describe a practice and ask for its pillar.
Well-Architected Framework · Going deeper · 1 of 2
Design principles: operations, security, reliability
Each pillar has design principles. Matching a principle to its pillar is a standard question.
Well-Architected Framework · Going deeper · 2 of 2
Design principles: performance, cost, sustainability
"Consumption model" is cost. "Serverless" and "go global" are performance. "Maximise utilisation" is sustainability.
Cloud Adoption Framework
Six perspectives ask whether the organisation is ready
The AWS CAF has six perspectives: Business, People, Governance, Platform, Security, Operations.
The Cloud Adoption Framework looks at the organisation, not the workload. It has six perspectives. Three are business capabilities. Business. People. Governance. Three are technical. Platform. Security. Operations. And it names the outcomes of adopting the cloud well: reduced business risk, improved environmental, social and governance performance, increased revenue, and increased operational efficiency.
Cloud Adoption Framework · Going deeper
Phases and stakeholders
Adoption moves through Envision, Align, Launch, Scale.
Migration strategies
Seven Rs, ordered by how much you change
From retire to refactor: the seven Rs differ in how much of the application changes.
For each application, a migrating company picks one of seven strategies. Retire it. Retain it where it is. Relocate the whole platform unchanged. Rehost: lift and shift the servers to EC2. This is the quickest real move. Replatform: make a few optimisations, such as moving the database to a managed service. Repurchase: replace it with a software-as-a-service product. Refactor: redesign it to be cloud native. That is the most work, and the most benefit.
Migration strategies · Going deeper
The migration tools
Application Migration Service moves servers. DMS moves databases. SCT converts schemas.
Check yourself
A team moves its app servers to EC2 unchanged, but swaps its self-run PostgreSQL for Amazon RDS. Which strategy is this?
Cloud economics
A fixed cost paid up front becomes a variable cost that follows use
Moving to AWS trades fixed (capital) expense for variable (operating) expense.
The last idea of domain one is economics. Owning capacity means buying it in large steps before you need it. The red line is flat, then jumps. That is a fixed cost: it is paid whatever happens. Renting follows what you actually use, month by month. That is a variable cost. In accounting terms, capital expense becomes operating expense. The space between the lines is capacity you own and do not use.
Cloud economics · Going deeper
The vocabulary of task 1.4
Rightsizing, BYOL, economies of scale and total cost of ownership are all asked by name.
Check yourself
Which practice belongs to the Reliability pillar?
Lesson complete
You finished “Why AWS: benefits, design principles and migration”
Answer the questions along the way to see your score here.