1.5. Reflection Checkpoint: First Principles of Cloud Computing

Key Takeaways

• Cloud computing shifts IT spending from capital expense (buying and maintaining hardware) to operational expense (paying only for what you use) — this single shift underpins nearly every other cloud benefit tested on the exam.
• The five characteristics (on-demand self-service, broad network access, resource pooling, rapid elasticity, measured service) explain why the cloud can absorb sudden demand spikes that would crash a fixed on-premises deployment.
• IaaS, PaaS, and SaaS mark a sliding scale of what you manage versus what the provider manages. Picking the wrong one means either taking on operational burden you didn't need, or giving up control you actually needed.
• Public, Private, and Hybrid deployment models trade off control, cost, and compliance differently — hybrid exists specifically to let sensitive data stay on-premises while less-sensitive workloads burst to the public cloud.

Connecting Forward

Phase 1 gave you the vocabulary and mental models for what cloud computing is and why it matters. Phase 2 puts that theory to work: you'll meet the specific AWS services (EC2, S3, VPC, RDS, IAM, and more) that implement these first principles, organized around AWS's global infrastructure of Regions and Availability Zones.

Self-Check Questions

• A company complains that their on-premises servers sit mostly idle except during a two-week seasonal spike each year. Which cloud characteristic most directly solves this, and why doesn't simply "buying a bigger server" solve it as well?
• A healthcare startup wants the low overhead of SaaS but must retain full control over patient data encryption and access policies. Which service model actually fits, and what does that reveal about the trade-off between "ease of use" and "control"?