Study guide
This first domain covers roughly a quarter of the AWS Certified Cloud Practitioner exam and sets the vocabulary for everything that follows: why organizations move to the cloud, how AWS wants you to design once you are there, and how a company actually gets its existing workloads off its own hardware and into AWS data centers. Expect scenario questions that ask you to match a business goal, such as reducing upfront spending or scaling for a surprise traffic spike, to the AWS concept that solves it.
The AWS Value Proposition
Cloud computing is the on-demand delivery of computing power, storage, and other IT resources over the internet, billed for what you actually consume. AWS describes its core benefits in a few recurring themes that the exam likes to test directly. Economies of scale means AWS purchases and operates data center hardware at a volume no single company could match, and it passes some of those savings to customers through lower unit prices over time. Elasticity is the ability to automatically add or remove computing capacity to match real-time demand, so a retailer named Harlow Goods can add web servers automatically during a flash sale and release them the moment traffic drops, paying only for the capacity actually used. Agility refers to the speed at which teams can provision new resources, experiment, and discard failed ideas without waiting weeks for physical hardware to arrive. AWS also converts capital expenditure, the large upfront purchase of servers a company owns and depreciates over years, into variable operating expenditure, the pay-as-you-go model where infrastructure cost tracks actual usage month to month. Finally, global reach lets a company deploy an application in multiple geographic areas within minutes, placing infrastructure closer to end users, which lowers latency, the delay between a request and its response. Together these ideas answer the exam's favorite framing question: why would a company choose AWS over building its own data center?
The Six Pillars of the AWS Well-Architected Framework
The AWS Well-Architected Framework is a set of questions and best practices for evaluating cloud architectures, organized into six pillars. Operational excellence covers running and monitoring systems to deliver business value, including automating changes and learning from failures through defined procedures. Security focuses on protecting data, systems, and assets through risk assessments and mitigation strategies, built on a foundation of identity management and traceability. Reliability is the ability of a workload to perform its intended function correctly and consistently, including recovering quickly from infrastructure or service disruptions. Performance efficiency means using computing resources efficiently to meet requirements and maintaining that efficiency as demand changes and technology evolves. Cost optimization is about running systems to deliver business value at the lowest price point, avoiding unnecessary spending. Sustainability, added as the sixth pillar, addresses minimizing the environmental impact of running cloud workloads, such as choosing regions with cleaner energy grids or improving utilization so fewer physical resources are needed overall. A useful way to remember these for the exam is that each pillar answers a different question about a workload: is it secure, does it stay up, is it fast, does it cost too much, is it efficiently operated, and is it environmentally responsible. Exam scenarios often describe a symptom, such as an application that goes down during a regional outage, and ask which pillar the fix belongs to; that example points to reliability.
AWS Cloud Adoption Framework and Migration Strategies
The AWS Cloud Adoption Framework (CAF) provides guidance for organizations planning a large-scale move to the cloud, organized into perspectives covering business, people, governance, platform, security, and operations concerns, so that a migration accounts for organizational change, not just technology change. When it comes to actually moving data and workloads, AWS offers several tools suited to different situations. AWS Snowball is a physical, ruggedized device that AWS ships to a customer's data center to transfer very large amounts of data, useful when a company like Denbury Logistics needs to move a petabyte of archived video and an internet transfer would take months. For ongoing data movement rather than a one-time bulk transfer, AWS Database Migration Service (DMS) replicates a running database to AWS with minimal downtime, and it can pair with the AWS Schema Conversion Tool when the source and target database engines differ. Migration strategies are summarized by AWS as the seven Rs: rehosting (moving an application as-is, sometimes called lift-and-shift), replatforming (making small optimizations without changing the core architecture), repurchasing (switching to a different product, often a SaaS alternative), refactoring (re-architecting the application to take fuller advantage of cloud-native features), retiring (decommissioning applications no longer needed), retaining (keeping certain systems on-premises for now), and relocating (moving infrastructure, such as VMware-based virtual machines, to the cloud without purchasing new hardware or changing the application). A scenario describing a company moving an application with zero code changes to get it running quickly is testing rehosting; a scenario describing a company rebuilding an application around serverless components is testing refactoring.
Cloud Economics: Costs, Licensing, and Rightsizing
Understanding how AWS costs behave compared to traditional data centers is a recurring exam theme. On-premises infrastructure carries fixed costs, largely capital expenditure on hardware that must be paid regardless of how much it is used, plus ongoing costs for facilities, power, and staff. Cloud infrastructure shifts much of this to variable cost, meaning the bill rises and falls with actual consumption, which matters when demand is unpredictable. Licensing choices add another dimension: with Bring Your Own License (BYOL), a customer uses software licenses it already owns or purchased separately, useful when a company has an existing enterprise agreement with a software vendor, while other AWS offerings bundle the license cost into the hourly service price, simplifying billing at a potentially higher per-hour rate. Rightsizing means matching resource types and sizes, such as EC2 instance types, to actual workload needs rather than over-provisioning out of caution, which directly reduces waste. Automation also reduces cost indirectly: AWS CloudFormation lets teams define infrastructure as code in template files, so environments are created consistently and can be torn down completely when not needed, avoiding the cost of forgotten resources left running. Choosing managed services over self-managed alternatives is another lever AWS emphasizes for both cost and operational efficiency. Amazon RDS manages routine database administration tasks such as patching and backups; Amazon ECS and Amazon EKS manage the control plane for running containers so a team does not operate that layer itself; and Amazon DynamoDB removes the need to provision or manage database servers at all for many key-value and document workloads. The exam favors the managed option whenever a question emphasizes minimizing operational overhead.
Key terms
- Elasticity
- — The capability to automatically scale computing resources up or down to match real-time demand.
- Economies of scale
- — Cost advantages AWS gains from operating infrastructure at massive volume, some of which are passed to customers as lower prices.
- Capital expenditure (CapEx)
- — Large upfront spending on physical assets, such as owned servers, typically depreciated over years.
- Operating expenditure (OpEx)
- — Ongoing, usage-based spending, such as pay-as-you-go cloud costs, rather than a large upfront investment.
- AWS Well-Architected Framework
- — A set of six pillars and associated best practices — operational excellence, security, reliability, performance efficiency, cost optimization, and sustainability — used to evaluate cloud architectures.
- AWS Cloud Adoption Framework (CAF)
- — Guidance organized into business, people, governance, platform, security, and operations perspectives to help organizations plan cloud adoption.
- AWS Snowball
- — A physical device shipped to a customer site for transferring large volumes of data into or out of AWS without relying on internet bandwidth.
- AWS Database Migration Service (DMS)
- — A service that migrates and replicates databases to AWS with minimal application downtime.
- Rehosting
- — A migration strategy, often called lift-and-shift, that moves an application to the cloud with little or no modification.
- Refactoring
- — A migration strategy that re-architects an application to take advantage of cloud-native features, often for long-term scalability.
- Bring Your Own License (BYOL)
- — A licensing model where a customer uses software licenses it already owns rather than paying for a license bundled into the service price.
- AWS CloudFormation
- — A service for defining and provisioning AWS infrastructure using code-based templates, enabling consistent, repeatable environments.
Exam tips
- When a question describes a business reason for moving to AWS (speed, elasticity, global reach, converting CapEx to OpEx), match it to the specific value-proposition term rather than a generic answer.
- If a scenario names a specific symptom (downtime, slow response, high bill, manual toil), identify which single Well-Architected pillar it maps to before picking an answer.
- Distinguish Snowball (physical bulk data transfer) from DMS (ongoing database replication) — the exam often swaps these into wrong-answer choices.
- Learn the 7 Rs migration vocabulary well enough to tell rehosting, replatforming, relocating, and refactoring apart from a one-sentence scenario.
- Favor managed services (RDS, ECS, EKS, DynamoDB) as the answer whenever a question stresses reducing operational or administrative burden.