Domain 1: Cloud Concepts
Topic 1 of 4 · Study notes
AWS Certified Cloud Practitioner (CLF-C02) — Domain 1: Cloud Concepts
Exam Code: CLF-C02 | Level: Foundational
Domain Weight: 24% | Total Domains: 4 | Passing Score: 700 / 1000
Table of Contents
- What is Cloud Computing
- Cloud Deployment Models
- Cloud Service Models
- Six Benefits of Cloud Computing
- AWS Global Infrastructure
- AWS Well-Architected Framework
- Cloud Economics and Total Cost of Ownership
- Migration Strategies — The 6 R's
- Exam Tips and Quick Reference
1. What is Cloud Computing
1.1 Definition and Core Idea
Cloud computing is the on-demand delivery of IT resources — compute, storage, databases, networking, analytics, machine learning, and software — over the internet with pay-as-you-go pricing.
Instead of purchasing and maintaining physical data centers and servers, organizations access technology services as needed from a cloud provider such as AWS. The provider owns the hardware; customers rent capacity.
Key Concept: The two defining characteristics of cloud computing are on-demand availability and pay-as-you-go pricing. Resources are provisioned in minutes and costs scale directly with usage.
1.2 Traditional IT vs Cloud Computing
| Aspect | Traditional IT (On-Premises) | Cloud Computing |
|---|---|---|
| Hardware ownership | Company purchases and owns all hardware | Provider owns hardware; customer rents |
| Cost model | High upfront capital expenditure (CapEx) | Ongoing operational expenditure (OpEx) |
| Scaling speed | Weeks to months (procurement and setup) | Minutes to seconds |
| Capacity planning | Must predict and over-provision | Provision on actual demand |
| Geographic expansion | Requires new data center investment | Deploy globally with a few clicks |
| Maintenance | Fully company's responsibility | Shared or fully provider's responsibility |
| Time to market | Slowed by infrastructure lead times | Infrastructure ready in minutes |
Key Concept: CapEx (Capital Expenditure) is a large upfront investment in physical assets. OpEx (Operational Expenditure) is a recurring cost based on consumption. Cloud computing converts CapEx to OpEx, freeing capital and reducing financial risk.
2. Cloud Deployment Models
2.1 Public Cloud
The cloud infrastructure is owned and operated by a third-party cloud provider and delivered over the internet. Multiple customers (tenants) share the same physical infrastructure, with logical isolation between them.
- No capital expenses to deploy or scale
- Applications can be provisioned and deprovisioned in minutes
- Customers pay only for what they use
- AWS Examples: Running EC2 instances, storing data in S3, deploying a Lambda function
2.2 Private Cloud
Cloud infrastructure used exclusively by a single organization. It may be physically located on-premises or hosted by a third party, but all services are maintained on a private network dedicated to that organization.
- Greater control over resources, security, and compliance configurations
- High upfront cost — similar economics to traditional IT
- Required by organizations with strict regulatory requirements (e.g., classified government systems)
- Examples: VMware vSphere environment, OpenStack deployment, AWS GovCloud for certain agencies
2.3 Hybrid Cloud
A combination of public and private clouds, with data and applications able to move between them as needed.
- Sensitive or regulated workloads remain on-premises; others run on public cloud
- Common during cloud migration phases
- Requires connectivity: AWS Site-to-Site VPN or AWS Direct Connect
- Example: A hospital stores patient records on-premises (HIPAA compliance) but runs analytics workloads on AWS
Exam Tip: When a scenario describes a company keeping some data on-premises for compliance while using AWS for other workloads, the answer is Hybrid Cloud. This is a frequently tested pattern.
3. Cloud Service Models
Cloud services are delivered in three models. Each model defines a different division of management responsibility between the customer and the provider. The further up the stack, the more the provider manages.
3.1 IaaS — Infrastructure as a Service
The provider delivers virtualized computing infrastructure over the internet. The customer manages the operating system and everything above it.
- Customer manages: OS, middleware, runtime, applications, data
- Provider manages: Physical hardware, networking, virtualization
- AWS Examples: EC2, EBS, VPC
- Analogy: Renting an empty apartment — the building exists, but you furnish it
Use cases: Test and development environments, custom application hosting, high-performance computing
3.2 PaaS — Platform as a Service
The provider delivers a complete development and deployment environment. The customer manages only the application code and data.
- Customer manages: Application code and data
- Provider manages: OS, runtime, middleware, hardware, scaling
- AWS Examples: AWS Elastic Beanstalk, AWS RDS (managed DB engine)
- Analogy: Renting a furnished apartment — infrastructure and platform are ready; you just move in
Use cases: Developers who want to focus on code without managing servers, web and API development
3.3 SaaS — Software as a Service
The provider delivers a complete software product managed and run on the provider's infrastructure. Users access the application via a browser or API.
- Customer manages: Nothing infrastructure-related; only user data and access
- Provider manages: Everything
- AWS Examples: Amazon Chime, Amazon WorkMail
- Analogy: Staying in a hotel — everything is provided and maintained
Use cases: Email, collaboration tools, CRM systems
3.4 Service Model Comparison
| Aspect | IaaS | PaaS | SaaS |
|---|---|---|---|
| Customer manages | OS, apps, data | Apps and data only | Nothing (use the software) |
| Provider manages | Hardware, networking | Hardware, OS, runtime | Everything |
| Control level | High | Medium | Low |
| Ease of use | Requires expertise | Moderate | Easiest |
| AWS Example | EC2 | Elastic Beanstalk | Amazon Chime |
4. Six Benefits of Cloud Computing
AWS formally defines six advantages of cloud computing. These appear directly in exam questions, often as the correct answer in scenario-based questions.
| # | Benefit | What It Means in Practice |
|---|---|---|
| 1 | Trade capital expense for variable expense | Pay only when you consume resources, only for how much you consume — no upfront hardware investment |
| 2 | Benefit from massive economies of scale | AWS's aggregate usage across hundreds of thousands of customers drives lower per-unit costs; customers benefit from AWS's purchasing power |
| 3 | Stop guessing capacity | Scale up or down in minutes based on actual demand; eliminate over-provisioning and under-provisioning waste |
| 4 | Increase speed and agility | New IT resources available in minutes, not weeks; dramatically reduces cost and time to experiment |
| 5 | Stop spending money on running data centers | Focus on projects that differentiate your business, not on racking, stacking, and powering servers |
| 6 | Go global in minutes | Deploy applications in multiple AWS Regions worldwide with a few clicks; provide lower latency to users globally |
5. AWS Global Infrastructure
5.1 Regions
A Region is a physical location in the world where AWS clusters multiple data centers. Each Region is a separate geographic area and operates independently — data stored in a Region does not leave that Region unless explicitly transferred by the customer.
AWS operates 30+ Regions globally, each identified by a code such as us-east-1 (US East, N. Virginia) or eu-west-1 (Europe, Ireland).
How to select a Region — four factors:
| Factor | Description |
|---|---|
| Compliance and data governance | Legal requirements may mandate data stays within a specific country (e.g., GDPR requires EU data to remain in the EU) |
| Latency | Choose the Region geographically closest to your end users for lowest latency |
| Service availability | Not all AWS services are available in all Regions; verify before designing architecture |
| Pricing | Costs vary slightly between Regions; compare for cost-sensitive workloads |
5.2 Availability Zones
An Availability Zone (AZ) is one or more discrete data centers with redundant power, networking, and connectivity, all located within a Region. AZs are physically separated — typically miles apart — and connected via low-latency, high-bandwidth, private fiber-optic links.
- Each Region contains a minimum of 3 AZs (most have 3–6)
- If one AZ fails due to power outage or disaster, the others continue operating
- Deploying across multiple AZs is the primary mechanism for high availability and fault tolerance on AWS
Region: us-east-1 (N. Virginia)
├── AZ: us-east-1a (one or more data centers)
├── AZ: us-east-1b (one or more data centers)
├── AZ: us-east-1c (one or more data centers)
└── AZ: us-east-1d (one or more data centers)
Exam Tip: AZs are for your application's availability. Deploy across multiple AZs to survive a data center failure. This is distinct from Edge Locations, which are for content delivery.
5.3 Edge Locations and Points of Presence
Edge Locations are data centers used by Amazon CloudFront (CDN) to cache content as close to end users as possible. With 400+ Edge Locations globally — far more than Regions — they ensure low-latency delivery.
How it works: A user in Tokyo requests a video hosted in S3 (us-east-1). CloudFront serves the cached copy from the nearest Edge Location in Tokyo instead of routing to the US — dramatically reducing latency.
Also used by: Amazon Route 53 (DNS), AWS Global Accelerator, and AWS Shield.
5.4 Additional Infrastructure Components
| Component | Description | Primary Use Case |
|---|---|---|
| Local Zones | Extensions of Regions placed in metro areas | Latency-sensitive workloads near large population centers (e.g., LA, Chicago) |
| Wavelength Zones | AWS compute embedded within 5G telecom networks | Ultra-low latency for mobile applications (AR/VR, gaming, real-time analytics) |
| AWS Outposts | AWS-managed physical racks installed on-premises | Run native AWS services in your own data center; data residency requirements |
5.5 Infrastructure Summary Table
| Component | Approximate Count | Purpose |
|---|---|---|
| Regions | 30+ | Geographic isolation, data sovereignty, major application deployments |
| Availability Zones | 90+ | High availability and fault tolerance within a Region |
| Edge Locations | 400+ | Low-latency content caching and delivery (CloudFront, Route 53) |
| Local Zones | 30+ | Extend Region services to specific metro areas |
| Wavelength Zones | Multiple | 5G mobile ultra-low latency applications |
| Outposts | Customer sites | On-premises AWS infrastructure extension |
6. AWS Well-Architected Framework
The Well-Architected Framework is AWS's guide for building secure, high-performing, resilient, and efficient cloud infrastructure. It consists of six pillars, each representing a set of foundational design principles and best practices.
6.1 The Six Pillars
| Pillar | Core Focus | Key Design Principles |
|---|---|---|
| Operational Excellence | Running and improving systems to deliver business value | Perform operations as code; make small, reversible changes; anticipate and learn from failures |
| Security | Protecting data, systems, and assets | Implement least privilege; enable traceability; encrypt data in transit and at rest; apply security at all layers |
| Reliability | Ability to recover from failures and meet demand | Automatically recover from failure; test recovery procedures; scale horizontally; stop guessing capacity |
| Performance Efficiency | Using resources efficiently as demand and technology evolve | Use serverless; go global in minutes; experiment frequently; use managed services |
| Cost Optimization | Delivering business value at the lowest price point | Adopt a consumption model; measure efficiency; eliminate unused resources; use the right pricing model |
| Sustainability | Minimizing environmental impact of cloud workloads | Maximize utilization; use managed services; adopt efficient hardware (e.g., AWS Graviton) |
Exam Tip: Know all six pillar names and their one-sentence focus. Exam questions often describe a scenario and ask which pillar is being addressed. Sustainability (added in 2021) is the newest and sometimes overlooked by candidates.
6.2 AWS Well-Architected Tool
A free tool available in the AWS Management Console that allows customers to review workloads against the six pillars, receive prioritized improvement recommendations, and track remediation progress over time. Available to all AWS accounts at no charge.
7. Cloud Economics and Total Cost of Ownership
7.1 CapEx vs OpEx
| Model | Description | Cloud Equivalent |
|---|---|---|
| CapEx | Large upfront investment in physical assets; depreciated over time | Buying and owning servers on-premises |
| OpEx | Recurring costs based on actual consumption; expensed in the period incurred | Paying for EC2 hours, S3 storage, and data transfer on AWS |
Cloud computing converts CapEx to OpEx. Organizations trade large, unpredictable capital commitments for predictable, usage-based spending.
7.2 Hidden On-Premises Costs
Many organizations underestimate on-premises TCO by failing to account for all cost components:
| Cost Category | Examples |
|---|---|
| Hardware | Servers, storage arrays, networking switches, cabling |
| Facilities | Data center real estate, leasing, physical security |
| Power and cooling | Electricity, UPS systems, HVAC, generators |
| IT staffing | Engineers for hardware maintenance, patching, break-fix |
| Refresh cycles | Hardware replacement every 3–5 years |
| Disaster recovery | Secondary site, replication infrastructure |
| Software licensing | OS licenses, virtualization platforms, management tools |
Note: The AWS Pricing Calculator (calculator.aws) is the tool for estimating expected AWS costs before deploying. It should not be confused with AWS Cost Explorer (analyzes past spending) or AWS Budgets (sets spending alerts).
7.3 AWS Pricing Models Overview
| Model | Commitment | Potential Savings | Best Suited For |
|---|---|---|---|
| On-Demand | None | None (baseline) | Unpredictable or short-term workloads |
| Savings Plans | 1 or 3 years (dollar spend) | Up to 66% | Flexible savings across compute types |
| Reserved Instances | 1 or 3 years (instance config) | Up to 72% | Steady-state, predictable workloads |
| Spot Instances | None (interruptible) | Up to 90% | Fault-tolerant, flexible, batch workloads |
| Dedicated Hosts | Optional 1 or 3 years | Varies | BYOL compliance, regulatory isolation |
8. Migration Strategies — The 6 R's
When migrating workloads to AWS, organizations choose a strategy for each application. Exam questions present a business scenario and ask which strategy applies.
| Strategy | Common Name | Effort | Description | Typical Example |
|---|---|---|---|---|
| Rehost | Lift and Shift | Low | Move application to AWS with no changes to architecture or code | On-premises VM migrated to EC2 as-is using AWS MGN |
| Replatform | Lift, Tinker, Shift | Medium | Make targeted cloud optimizations without changing core architecture | Migrating MySQL running on EC2 to managed Amazon RDS |
| Repurchase | Drop and Shop | Low | Replace existing application with a cloud-native or SaaS product | Replacing on-premises CRM with Salesforce; Exchange with Microsoft 365 |
| Refactor / Re-architect | — | High | Redesign the application from scratch using cloud-native capabilities | Breaking a monolith into microservices running on Lambda and containers |
| Retire | — | None | Decommission applications no longer needed | Redundant or unused apps discovered during portfolio assessment |
| Retain | Revisit | None | Keep on-premises for now — too complex, recently updated, or compliance-sensitive | Legacy mainframe awaiting a future migration phase |
Exam Tip: Rehost = fastest migration, least cloud benefit. Refactor = most effort, greatest long-term cloud benefit. Retire = reduces portfolio size and cost immediately with zero migration work.
9. Exam Tips and Quick Reference
Scenario-to-Answer Mapping
| Scenario Keyword or Requirement | Correct Answer / Concept |
|---|---|
| "Keep some data on-premises, use AWS for the rest" | Hybrid Cloud |
| "Fastest way to migrate with no code changes" | Rehost (Lift and Shift) |
| "Replace on-premises email with cloud email" | Repurchase |
| "Modernize application using serverless and microservices" | Refactor / Re-architect |
| "Survive a single data center failure" | Deploy across multiple Availability Zones |
| "Reduce latency for global users" | Deploy in multiple Regions; use CloudFront Edge Locations |
| "Estimate cost before building on AWS" | AWS Pricing Calculator |
| "Company moved from buying servers to paying monthly" | CapEx to OpEx shift |
| "Which pillar covers reducing environmental impact" | Sustainability pillar |
| "Which service is on-premises AWS infrastructure" | AWS Outposts |
Common Exam Traps
- Region vs AZ vs Edge Location: Regions are for deploying applications with data sovereignty control. AZs are for fault tolerance within a Region. Edge Locations are for CDN caching — not for application deployment.
- IaaS vs PaaS: EC2 is IaaS (you manage the OS). RDS and Elastic Beanstalk are PaaS (AWS manages the OS and runtime). Many candidates misclassify RDS as IaaS.
- Savings Plans vs Reserved Instances: Both offer up to ~72% discount. Savings Plans are more flexible (commit to dollar spend, not a specific instance). RIs are instance-specific.
Key Terms — Domain 1
| Term | Definition |
|---|---|
| Cloud Computing | On-demand delivery of IT resources over the internet with pay-as-you-go pricing |
| CapEx | Capital Expenditure — large upfront investment in physical infrastructure |
| OpEx | Operational Expenditure — recurring costs based on consumption |
| Region | A geographic cluster of AWS data centers, fully independent from other Regions |
| Availability Zone | One or more data centers within a Region, isolated for fault tolerance |
| Edge Location | Site used by CloudFront to cache content closer to end users |
| High Availability | System design ensuring minimal downtime through redundancy across AZs |
| Fault Tolerance | Ability to continue operating despite component failures |
| Elasticity | Automatic scaling of resources up or down in response to demand |
| Scalability | Ability to handle growing workload by adding resources |
| TCO | Total Cost of Ownership — full cost analysis including all direct and hidden costs |
| Well-Architected Framework | AWS best-practice guide built on six pillars for cloud architecture |
End of Domain 1. Continue to Domain 2: Security and Compliance →
Ready to test yourself?
Practice questions for this topic