Cloud Concepts & Service Models

Cloud computing is the on-demand delivery of IT resources — compute, storage, databases, networking, and more — over the internet with pay-as-you-go pricing. AWS operates the physical infrastructure while customers consume only the capacity they need, replacing large upfront capital expenses with variable operational costs. The CLF-C02 exam tests the six advantages: trade capital expense for variable expense, benefit from massive economies of scale, stop guessing capacity, increase speed and agility, stop spending on running data centers, and go global in minutes. Provisioning that once took weeks now happens in minutes.

Infrastructure as a Service provides virtualized compute, storage, and networking, leaving the customer responsible for the operating system, middleware, runtime, and applications. AWS EC2 is the canonical example: AWS owns the physical servers and hypervisor, but the customer selects the AMI, patches the OS, configures security groups, and manages everything on the instance. IaaS sits at the bottom of the service-model stack, giving the most flexibility and the most operational burden. The exam “watch out”: moving from IaaS to PaaS (such as AWS Elastic Beanstalk) shifts OS-level patching to AWS.

Platform as a Service sits between IaaS and SaaS. The provider manages the infrastructure, operating system, runtime, and middleware, leaving the customer responsible only for application code and data. AWS Elastic Beanstalk is the canonical PaaS example on CLF-C02: you upload code and it provisions capacity, a load balancer, and auto scaling. Amazon RDS shows PaaS traits since AWS handles the engine, patching, and backups. The exam contrast is with IaaS (EC2), where you keep OS-level control and apply patches yourself.

Software as a Service delivers fully functional applications over the internet, with the cloud provider managing every layer: hardware, networking, operating system, runtime, middleware, and the application itself. The customer simply uses the software through a browser or thin client. An AWS example is Amazon WorkMail, and many third-party SaaS products are available through AWS Marketplace. Under the shared responsibility model the provider handles nearly everything, leaving the customer responsible mainly for their own data and user access. This contrasts with IaaS, where the customer manages the OS upward, and PaaS, where the customer manages only their application and data.

The AWS Well-Architected Framework is a structured set of design principles and best practices organized into six pillars: operational excellence, security, reliability, performance efficiency, cost optimization, and sustainability. AWS publishes it as both a whitepaper and an interactive tool — the AWS Well-Architected Tool in the console — that lets teams review workloads against each pillar through guided question-and-answer sessions.

A common CLF-C02 trap is confusing the framework with AWS Trusted Advisor. Trusted Advisor automates specific checks (cost optimization, security, fault tolerance, performance, service limits) and surfaces actionable alerts, whereas the Well-Architected Tool is a deeper, customer-driven architectural review. Both relate to best practices but operate at different levels of depth and automation.

Pay-as-you-go means AWS charges only for the compute, storage, and data transfer actually consumed during a billing period, with no upfront purchase and no minimum usage fee required. This converts infrastructure spending from capital expenditure (CapEx) into operational expenditure (OpEx), shifting the model from owning assets to renting capacity on demand. The key exam nuance is that pay-as-you-go is AWS’s default pricing model, but it is not always the cheapest. Reserved Instances and Savings Plans offer lower effective rates in exchange for a usage commitment, so a steady, predictable workload may favor a commitment-based model instead.

Agility in cloud computing is the capacity to rapidly provision, experiment with, and decommission resources as business needs change. On AWS, what once took weeks of procurement and data-center setup happens in minutes through the console, CLI, or infrastructure-as-code tools like AWS CloudFormation. CLF-C02 often tests agility versus elasticity: elasticity is the automatic scaling of capacity to match workload fluctuations, while agility is the broader organizational speed advantage — testing ideas cheaply, failing fast, and iterating without large upfront commitments. Both reduce time to market, but agility operates at the business and development-cycle level, not just the infrastructure layer.