Six advantages

AWS names six benefits, and the exam quotes them

AWS's wordingIn your own data centreOn AWS1Trade fixed expense for variable expensebuy servers before you know you need thempay only for what you use, as you use it2Benefit from massive economies of scaleyour own small purchasing powerAWS's volume turns into lower prices3Stop guessing capacitytoo much sits idle, too little turns users awayscale up or down in minutes4Increase speed and agilityweeks to get a new serverminutes, so experiments are cheap5Stop spending money on data centresracking, powering and coolingyour people work on your product6Go global in minutesbuild a site in each countrydeploy to any Region with a few clicksAWS states six advantages of cloud computing, and the exam quotes them almost word for word.Learn the left-hand column as written. A question describes the situation in the middle column and asks whichadvantage answers it. The usual trap is an advantage that is true but answers a different problem: "go global"offered for a capacity problem, or "economies of scale" for a speed problem.

The six advantages of cloud computing are the stock answers of domain 1. Learn them as worded.

Six advantages · Going deeper

Eight words the options are built from

The wordWhat it meansHow it shows upHigh availabilitystays up when a part failstwo Availability Zones behind a load balancerFault toleranceno interruption at all when a part failsstricter and dearer than high availabilityElasticitygrows and shrinks with demand by itselfAuto Scaling adds and removes instancesScalabilitycan grow to handle more loadup (bigger machine) or out (more machines)Agilitynew resources and changes in minutestry an idea today, discard it tomorrowDurabilitystored data is not lostS3 is designed for 99.999999999% (11 nines)Reliabilitydoes the right thing consistently, and recoversa Well-Architected pillarGlobal reachserve users from a Region near themlower latency, local data residencyThese eight words are the answer options of domain 1. Each has one meaning; do not let them blur.Elasticity and scalability differ: scalable means it can grow, elastic means it also shrinks without being told.

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

Fixed capacity, bought for the evening peak (one illustrative day for an online shop)idle, and paid for: 54% of itdemand00:0006:0012:0018:0000:00Elastic capacity follows the purple line, so the red area is money you no longer spend.A data centre must be sized for the busiest hour and is paid for every hour. On AWS, Auto Scaling adds servers asthe evening peak builds and removes them afterwards. This one picture is three of the six advantages at once:stop guessing capacity, trade fixed for variable expense, and increase agility.

Sized for the peak, this fixed capacity sits about 54% idle. Elastic capacity does not.

Check yourself

on salerequests over one day

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

A well-architected workloadOperationalexcellenceCan we run it, seeinto it and improve it?1SecurityAre data, systems andidentities protected?2ReliabilityDoes it keep working,and recover by itself?3PerformanceefficiencyAre we using the rightresources for the job?4CostoptimizationAre we paying onlyfor what gives value?5SustainabilityHow little energy andhardware can it use?6The Well-Architected Framework is six pillars. The exam gives a practice and asks which pillar it belongs to.It is AWS's checklist for judging any workload. Each pillar is one question. To place a practice, ask which questionit answers: "automatically recover from failure" answers Reliability; "run operations as code" answers Operationalexcellence. The Well-Architected Tool in the console walks a team through the review for free.

Know the six pillars by name and by the question each asks.

Well-Architected Framework · Going deeper · 1 of 2

Design principles: operations, security, reliability

Operational excellence·Perform operations as code·Make frequent, small, reversible changes·Anticipate failure, and learn from every operational failureSecurity·Implement a strong identity foundation; apply security at all layers·Enable traceability; protect data in transit and at rest·Keep people away from data; prepare for security eventsReliability·Automatically recover from failure; test recovery procedures·Scale horizontally to increase aggregate availability·Stop guessing capacity; manage change through automationDesign principles in AWS's own words. Exam options are lifted from these lists.

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

Performance efficiency·Democratise advanced technologies: use them as a service·Go global in minutes; use serverless architectures·Experiment more often; consider mechanical sympathyCost optimization·Adopt a consumption model: pay only for what you use·Measure overall efficiency; analyse and attribute expenditure·Stop spending money on undifferentiated heavy liftingSustainability·Understand your impact; set sustainability goals·Maximise utilisation; use managed services·Adopt more efficient hardware and software as they appearSustainability was added in 2021 as the sixth pillar. Older study material lists only five.

"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

Business capabilitiesTechnical capabilitiesBusinesscloud investment speeds upbusiness outcomesPeopleculture, structure, leadershipand skillsGovernancebenefits maximised, risk keptlowPlatforma scalable, hybrid cloudplatformSecurityconfidentiality, integrity,availabilityOperationsservices delivered at theagreed levelLeads toReduced business riskImproved ESG performanceIncreased revenueIncreased operational efficiencyThe Cloud Adoption Framework asks whether the organisation is ready, across six perspectives.Well-Architected judges a workload; the CAF judges the company that is moving. Three perspectives are about thebusiness and three about technology. The four outcomes in green are the benefits the exam guide names.

The AWS CAF has six perspectives: Business, People, Governance, Platform, Security, Operations.

Cloud Adoption Framework · Going deeper

Phases and stakeholders

The four phases of adoptionEnvisiontie cloud tobusiness outcomesAlignfind capability gapsand dependenciesLaunchdeliver pilotsin productionScaleexpand pilots tothe desired scalePerspectiveWho it speaks toBusinesschief executive, finance, operations, information and technology officersPeoplehuman resources, chief information and operating officers, functional leadersGovernancechief transformation, information, data, risk and financial officersPlatformchief technology officer, architects and engineersSecuritychief information security officer, compliance and audit leadersOperationsinfrastructure and operations leaders, site reliability engineersCAF in one line: six perspectives, four phases (Envision, Align, Launch, Scale), four business outcomes.

Adoption moves through Envision, Align, Launch, Scale.

Migration strategies

Seven Rs, ordered by how much you change

StrategyWhat you doHow much changesRetireswitch it offnothing movesRetainleave it where it is, for nownothing movesRelocatemove the platform unchanged, e.g. VMware to AWSRehost"lift and shift": same servers, on EC2Replatform"lift, tinker and shift": e.g. database to RDSRepurchase"drop and shop": replace with SaaSRefactorre-architect to be cloud nativeThe seven Rs are seven answers to "what shall we do with this application?", from nothing to a rewrite.More change costs more effort and gives more cloud benefit. Rehost is the fastest way in and the most commonfirst step. Bars show relative effort and are illustrative. Clue words: "without changes" is rehost; "move to amanaged database" is replatform; "move to a SaaS product" is repurchase; "microservices" is refactor.

From retire to refactor: the seven Rs differ in how much of the application changes.

Migration strategies · Going deeper

The migration tools

When the question saysThe service isBecause it"gather data about our on-premises servers"AWS Application Discovery Serviceinventories servers and dependencies"build the business case"Migration Evaluatorprojects AWS cost from current usage"track every migration in one place"AWS Migration Hubone dashboard across tools"lift and shift servers"AWS Application Migration Servicereplicates servers to EC2"migrate a database with little downtime"AWS Database Migration Servicecopies and keeps replicating data"change database engine"AWS Schema Conversion Toolconverts schema and code, then DMS"proven patterns and guides"AWS Prescriptive Guidancestrategies written by AWS experts"someone to do it for us"AWS Partners, Professional Servicespeople, not a toolDatabase replication, named in the exam guide, means DMS keeping source and target in step until cut-over.Same engine (MySQL to MySQL) needs DMS only. A different engine (Oracle to Aurora) needs SCT first, then DMS.

Application Migration Service moves servers. DMS moves databases. SCT converts schemas.

Check yourself

App serversunchangedAmazon EC2PostgreSQLself-runnow managedAmazon RDS

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

Owned: bought in steps, ahead of needsecond purchaseRented: follows what is used (illustrative)startyear 1year 2year 3Fixed cost (capital expense)paid up front, whatever happensVariable cost (operating expense)rises and falls with useCloud economics is one swap: a fixed cost paid up front becomes a variable cost that follows use.Owning means buying in large steps before you need them, and guessing. Renting tracks real use month by month.The gap between the two lines is capacity paid for and not used. The exam calls this trading fixed expense forvariable expense, or capital expense for operating expense.

Moving to AWS trades fixed (capital) expense for variable (operating) expense.

Cloud economics · Going deeper

The vocabulary of task 1.4

The termIn plain wordsWhat to rememberTotal cost of ownershipeverything owning really costshardware, space, power, cooling, staff, refreshEconomies of scaleAWS buys for millions of customersand has cut prices many times as it grewRightsizingmatch instance size to real useCompute Optimizer recommends sizesAutomationscripts and templates in place of handsfewer errors, less labour, resources off at nightBring Your Own License (BYOL)reuse licences you already ownoften needs Dedicated Hosts for per-core termsLicence includedAWS bundles the licence in the pricesimple; you pay for it by the hourManaged servicesAWS runs the undifferentiated workfewer staff hours per workloadTask statement 1.4 is this vocabulary. A question describes a saving and asks for its name.

Rightsizing, BYOL, economies of scale and total cost of ownership are all asked by name.

Check yourself

OperationalexcellenceSecurityReliabilityPerformanceefficiencyCostoptimizationSustainability

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.

Open in a new tab