Cloud computing fundamentally changes how companies use technology by letting them rent computing resources like servers, storage, and databases over the internet instead of buying and managing physical hardware. For the CLF-C02 exam, you must understand this shift from capital expense to variable expense, the benefits it delivers, and the core model of on-demand self-service. This concept underpins every other topic you will study in the AWS certification.
Jump to a section
A restaurant kitchen is a perfect analogy for cloud computing. In a traditional setup, each chef owns all their equipment – every pot, pan, knife, and spice rack. They must buy, maintain, and store everything themselves, even if they only need a specific pan once a month. The kitchen is crowded, costly, and inefficient, with equipment sitting idle most of the time.
Now imagine a shared commercial kitchen. A company called 'KitchenCloud' owns the building, all the ovens, mixers, and fridges. Chefs from different restaurants rent only what they need, when they need it. Chef A might rent a single burner for an hour to simmer a sauce, paying only for that time. Chef B, running a busy bakery, might lease an industrial mixer for the whole week and add more ovens as orders pour in for a holiday rush. KitchenCloud handles repairs, upgrades, and cleaning. If Chef C needs extra space for a big catering job, they can instantly rent a second prep station – they don't have to build a new kitchen. When the job is done, they stop renting it. The chefs avoid huge upfront costs (buying an oven is expensive), reduce waste (no idle equipment), and can scale up or down effortlessly. This is exactly how cloud computing works: you access computing power, storage, and software on demand from a provider's massive pooled resources, paying only for what you use, and scaling instantly without managing physical hardware.
Cloud computing is a model for enabling ubiquitous, convenient, on-demand network access to a shared pool of configurable computing resources (for example, networks, servers, storage, applications, and services) that can be rapidly provisioned and released with minimal management effort or service provider interaction. This formal definition from the US National Institute of Standards and Technology (NIST) captures the essential characteristics. Before the cloud, companies ran their own data centres. They bought physical servers, installed cables, set up air conditioning, and hired staff to monitor and repair the hardware. This model is called on-premises (or on-prem) infrastructure. It involved large upfront capital expenditure (CapEx) – buying a server might cost thousands of pounds – and ongoing operational costs for electricity, cooling, and maintenance. Scaling was slow: to handle a surge in users, you had to order, wait for delivery, and install new hardware, which could take weeks or months.
Cloud computing solves these problems by offering five essential characteristics as defined by NIST: On-demand self-service – users can provision computing capabilities (like a virtual server or storage) automatically without requiring human interaction with the provider. Broad network access – resources are available over the network and can be accessed by standard mechanisms that promote use by heterogeneous platforms (e.g., mobile phones, laptops, workstations). Resource pooling – the provider's computing resources are pooled to serve multiple consumers using a multi-tenant model, with different physical and virtual resources dynamically assigned and reassigned according to consumer demand. There is a sense of location independence – the customer generally has no control or knowledge over the exact location of the provided resources but may be able to specify location at a higher level of abstraction (e.g., country, region, or availability zone). Rapid elasticity – capabilities can be elastically provisioned and released, in some cases automatically, to scale rapidly outward and inward commensurate with demand. To the consumer, the capabilities available for provisioning often appear to be unlimited and can be appropriated in any quantity at any time. Measured service – cloud systems automatically control and optimise resource use by leveraging a metering capability at some level of abstraction appropriate to the type of service (e.g., storage, processing, bandwidth, and active user accounts). Resource usage can be monitored, controlled, and reported, providing transparency for both the provider and consumer of the utilised service.
AWS delivers these characteristics through three core service models: Infrastructure as a Service (IaaS) – you rent virtual machines, storage, and networks. You control the operating system, applications, and some networking components, but AWS manages the physical hardware. Platform as a Service (PaaS) – you deploy your applications without managing the underlying infrastructure. AWS handles the runtime, middleware, and OS. An example is AWS Elastic Beanstalk, where you upload your code and AWS runs it. Software as a Service (SaaS) – you use a complete application hosted by the provider. Examples include Amazon WorkDocs (document storage) or Salesforce. You do not manage anything except your data and user settings.
The value proposition of the AWS Cloud revolves around six key benefits: Trade capital expense for variable expense – instead of a heavy upfront investment in data centres and servers, you pay only for what you consume. Benefit from massive economies of scale – AWS aggregates usage from hundreds of thousands of customers, achieving lower per-unit costs that are passed on to you. Stop guessing capacity – you no longer need to predict your infrastructure needs. You can launch exactly the amount you need now and scale up or down as demand changes. Increase speed and agility – new IT resources are just a click away. You can spin up a server in minutes instead of weeks. Stop spending money on running and maintaining data centres – focus your team on building applications that differentiate your business instead of racking and stacking servers. Go global in minutes – deploy your application in multiple geographic regions around the world with a few clicks, providing lower latency and better customer experience.
Cloud computing is not a single technology but a paradigm shift. It requires a shared responsibility model: AWS secures the cloud (the physical infrastructure, hardware, and software that run its services), while you are responsible for security in the cloud (configuring your virtual machines, managing access to your data, and patching your operating system). Understanding this model is critical for the exam. The cloud's pay-as-you-go model also changes financial planning: you practice cost optimisation by using rightsizing (choosing the correct instance size), reserved instances (committing to a one- or three-year term for a discount), and auto-scaling (automatically adding or removing capacity based on load). Remember, cloud computing is not about avoiding servers – it is about abstracting them so you interact only with what you need, when you need it, without seeing the complexity underneath.
Assess current on-premises environment
The organisation evaluates its existing hardware, software, and workloads. This includes documenting server utilisation, dependencies, and performance needs. This step determines which workloads are suitable for migration and which are not.
Choose a migration strategy (6 R's)
Based on the assessment, decide for each application whether to rehost (lift-and-shift), replatform (make minor cloud optimisations), refactor (re-architect using cloud-native services), repurchase (move to a SaaS product), retire (decommission unused systems), or retain (keep on-premises). This step aligns the migration with business goals.
Provision cloud infrastructure using IaC
Define the cloud environment in code using tools like AWS CloudFormation. This includes setting up the VPC, subnets, security groups, and IAM roles. IaC ensures repeatable and consistent deployments, reducing human error.
Migrate data and applications
Use services like AWS Database Migration Service (DMS) or AWS Snowball for large datasets. For servers, create AMI images and launch EC2 instances. Test that applications function correctly in the new environment before cutting over traffic.
Optimise and monitor
After migration, use AWS tools like CloudWatch for monitoring, Trusted Advisor for best-practice checks, and Cost Explorer for spending analysis. Adjust auto-scaling policies and reserved instances to balance cost and performance. Continuously refine configurations.
Consider a mid-sized e-commerce company, 'BrightBuy', that sells furniture online. BrightBuy has historically run its own data centre: a room full of servers, switches, and storage arrays in their office basement. The IT team of four spends most of its time patching operating systems, swapping failed hard drives, and monitoring cooling systems. When a new product line launches, they must order a new server six weeks in advance. Traffic is predictable only during the day; overnight, 70% of their servers sit idle but still burn electricity and need maintenance.
BrightBuy decides to migrate to the AWS Cloud. Here is a realistic step-by-step scenario of what an IT professional does: First, they assess their current environment. They document every server, its operating system, its role (web server, database server, application server), and its utilisation. They use AWS Application Discovery Service to gather data automatically. Next, they plan the migration strategy using the six R's: Rehost (lift and shift – move servers as-is to Amazon EC2 instances), Replatform (make minor optimisations, like moving a database to Amazon RDS to offload patch management), Refactor (re-architect the application to use serverless services like AWS Lambda and Amazon API Gateway), Repurchase (move to a SaaS product, e.g., from a custom CRM to Salesforce), Retire (decommission unused servers), and Retain (keep some workloads on-premises). For BrightBuy, most web and application servers are rehosted to EC2 instances, and the MySQL database is replatformed to Amazon RDS for automated backups and patching.
Then they build the cloud infrastructure using Infrastructure as Code (IaC) with AWS CloudFormation or Terraform, defining everything in configuration files: virtual private cloud (VPC) with public and private subnets, security groups (virtual firewalls), and internet gateways. They set up auto-scaling groups so that during the Black Friday sale, the system automatically launches 20 additional web servers based on CPU utilisation thresholds. Load balancers distribute traffic evenly. They configure Amazon CloudWatch to monitor every metric – CPU, memory, disk I/O, and network traffic – and set alarms that trigger actions like email notifications or auto-scaling events. For security, they implement AWS Identity and Access Management (IAM) to create users, groups, and roles with least-privilege permissions. They enable AWS CloudTrail to log every API call for auditing. Finally, they cut over: they change DNS records to point the public domain to the new AWS application load balancer. The migration takes three weeks, and after cutover, BrightBuy's IT team no longer spends weekends racking servers. They focus on deploying new features, like a personalised recommendation engine, because they can experiment with new instances in minutes. Costs drop by 40% because they no longer pay for idle capacity – auto-scaling ensures they only run what they need. The team also uses AWS Cost Explorer to analyse spending and identify further savings, such as Reserved Instances for their steady-state database servers.
The CLF-C02 exam tests your understanding of cloud computing fundamentals, especially the definitions, benefits, and value proposition. Questions in this domain expect you to distinguish between cloud and on-premises, recognise the six benefits of AWS Cloud, and identify the five essential characteristics. You will see multiple-choice questions that present a scenario and ask: 'Which of the following is a benefit of cloud computing?' or 'What does it mean that cloud computing is 'elastic'?'. Another common format gives you a list of statements and asks which one correctly describes a characteristic.
Key definitions to memorise: On-demand self-service – you provision resources automatically without requiring human interaction. Broad network access – accessible via standard internet protocols. Resource pooling – provider serves multiple customers from shared resources. Rapid elasticity – scale up and down quickly, often automatically. Measured service – pay only for what you consume, with metering and reporting. Also, the six value propositions: trade CapEx for OpEx (variable expense), economies of scale, stop guessing capacity, increase speed and agility, stop data centre operations, and go global in minutes.
Traps the exam sets: They may ask about 'the ability to provision resources without human interaction' – the correct term is 'on-demand self-service', not 'automation' or 'elasticity'. They might offer 'pay for the resources in advance' as a benefit – that is wrong; cloud is pay-as-you-go, not prepaid for unused capacity. They could confuse 'resource pooling' with 'multi-tenancy' – they are related but resource pooling is the mechanism, multi-tenancy is the outcome. Another trap: 'cloud computing means you no longer need to worry about security' – false; security is a shared responsibility. The exam loves to test 'Which of the following is NOT a benefit of cloud computing?' and list false benefits like 'increased hardware management' (bad) or 'fixed monthly cost regardless of usage' (not true). Also, remember that 'cloud computing' includes all three service models (IaaS, PaaS, SaaS) – they may ask you to differentiate them in a scenario. For example, 'A company uses a database service where they manage their own schema but not the server' – that is PaaS (RDS), not IaaS (EC2 with self-managed DB).
Studying for this section: Practise recognising the definitions word-for-word. Flash cards for each term. Review the AWS Well-Architected Framework's six pillars (operational excellence, security, reliability, performance efficiency, cost optimisation, sustainability) – especially cost optimisation and performance efficiency, which map directly to cloud benefits. Expect at least 3-5 questions on this foundational knowledge in the exam. Focus on the direct, unambiguous definitions – AWS exams reward exact knowledge, not general intuition.
Cloud computing allows you to provision and release IT resources on demand over the internet, paying only for what you use.
The five essential characteristics of cloud computing are on-demand self-service, broad network access, resource pooling, rapid elasticity, and measured service.
The six benefits of the AWS Cloud are trade CapEx for variable expense, economies of scale, stop guessing capacity, increase speed and agility, stop data centre operations, and go global in minutes.
Cloud computing operates under a shared responsibility model: AWS secures the cloud infrastructure, and you secure your configurations and data within the cloud.
Scalability in cloud computing refers to handling increased load by adding resources (scale out) or increasing capacity (scale up), while elasticity refers to automatically adjusting resources up or down based on demand.
Understanding the difference between IaaS, PaaS, and SaaS is essential: IaaS gives you control over the OS and applications, PaaS abstracts the runtime and middleware, and SaaS provides a fully managed application.
These come up on the exam all the time. Here's how to tell them apart.
On-premises (Traditional IT)
High upfront capital expenditure (CapEx) for hardware
Fixed capacity that is hard to change quickly
You are responsible for all security and maintenance
Cloud Computing
Variable operational expenditure (OpEx) based on usage
Elastic capacity that scales up and down automatically
Shared responsibility: AWS secures the cloud, you secure your workloads
IaaS (Infrastructure as a Service)
You manage the operating system, middleware, and applications
Provides virtual machines, storage, and networks
More flexibility but higher management overhead (patching, scaling)
PaaS (Platform as a Service)
You only manage your applications and data
Provider manages the runtime, middleware, and OS
Less management overhead but less control over the environment
Vertical Scaling (Scale Up)
Increasing the capacity of an existing server (e.g., more RAM, CPU)
Limited by the maximum size of the largest server available
Often involves downtime during the upgrade
Horizontal Scaling (Scale Out)
Adding more servers to distribute the load
Virtually unlimited potential by adding many instances
Usually no downtime if implemented with a load balancer
Mistake
Cloud computing is just outsourcing your IT hardware to a different building.
Correct
Cloud computing is a service model with specific characteristics: on-demand self-service, broad network access, resource pooling, rapid elasticity, and measured service. It is not simply colocation; you can provision and release resources programmatically without dealing with physical hardware at all.
Many beginners equate 'cloud' with any remote server. The exam expects precise terminology and the distinction from traditional hosting or colocation.
Mistake
If you use the cloud, you do not need an internet connection to access your resources.
Correct
Broad network access means resources are available over the network using standard protocols. Without internet (or a dedicated network connection like AWS Direct Connect), you cannot access AWS services. The cloud is inherently network-dependent.
People sometimes think 'the cloud' is a magical place that works offline, but the defining feature is network-based access.
Mistake
Cloud computing always costs less than on-premises infrastructure.
Correct
Cloud computing can save money through economies of scale and variable costs, but it is not universally cheaper. For predictable, steady-state workloads running 24/7 for years, reserved instances or on-premises may be more cost-effective. The benefit is flexibility and agility, not guaranteed cost reduction.
Marketing often emphasises cost savings, but the exam tests that cost optimisation requires active management (rightsizing, reservations, etc.).
Mistake
In the cloud, you share physical servers with other customers, so your neighbour's workload affects your performance.
Correct
AWS uses hypervisor-level isolation: each virtual machine (instance) is isolated from others on the same physical host. AWS designs its infrastructure so that noisy neighbour effects are minimised by features like dedicated instances (if needed) and proper instance sizing. By default, performance is predictable.
The term 'shared resources' makes beginners worry about interference. The reality is robust isolation, and the exam expects understanding that shared physical infrastructure does not mean shared performance.
Reveal each answer, then mark whether you got it right. Score 60%+ to unlock the next chapter.
On-premises means you own and manage your own physical servers, storage, and networking equipment in your own building. Cloud computing means you rent these resources from a provider like AWS, accessing them over the internet, and you only pay for what you use.
Not necessarily. Cloud computing has user interfaces (the AWS Management Console) that allow non-programmers to launch resources manually. However, many best practices involve scripting and Infrastructure as Code, so basic programming skills help but are not mandatory for the exam.
Yes, but security is a shared responsibility. AWS provides strong physical and logical security for its infrastructure. You must configure your own security groups, IAM policies, and data encryption to secure your data. The exam teaches the shared responsibility model in detail.
Elasticity is the ability to automatically add or remove computing resources (like servers) to match the current demand. For example, during a traffic spike, new instances are launched; when traffic drops, they are terminated. This prevents overprovisioning and underutilisation.
Most applications can run in the cloud, but some legacy applications that depend on specific hardware or low-latency connections to on-premises systems may need re-architecting or are better left on-premises. The exam covers scenarios where serverless or containerised apps are more suitable.
AWS charges on a pay-as-you-go model: you pay only for the resources you actually use, measured per hour or per second for compute, and per GB for storage. There are no upfront costs unless you choose Reserved Instances for a discount.
You've just covered Cloud Computing Overview — now see how well it sticks with free CLF-C02 practice questions. Full explanations included, no account needed.
Done with this chapter?