You have probably heard "cloud computing" mentioned in news articles or job listings. But what does it actually mean?
This article explains what the cloud is, why companies are rushing to adopt it, and how these ideas show up on the AWS Cloud Practitioner exam. No IT background required — by the end of this article you will have a solid grasp of the fundamentals.
---
The Cloud in One Sentence
When you use electricity at home, you don't build your own power plant. You plug in, use what you need, and pay the bill at the end of the month.
Cloud computing works the same way. Instead of buying and managing physical servers, you rent computing power, storage, and networking over the internet — use what you need, pay for what you use, and stop when you're done.
In the old days, a company that needed a server had to buy hardware, ship it to a data center, connect the network, and install the operating system. That process took weeks or even months. With the cloud, you can start in minutes.
---
Three Service Models — IaaS, PaaS, SaaS
Cloud services are divided into three categories based on how much you manage yourself. Let's use everyday analogies to make it clear.
---
IaaS — Renting an Empty Office
IaaS (Infrastructure as a Service) gives you the raw infrastructure: servers, networking, and storage. The building is provided, but you arrange the furniture and set up everything inside.
You are responsible for installing the operating system and deploying your application. Amazon EC2 is the classic example of IaaS on AWS.
---
PaaS — Moving Into a Fully Furnished Co-Working Space
PaaS (Platform as a Service) goes one step further. The operating system and runtime environment are already set up. You only need to bring your application code — like walking into a co-working space where the desks, internet, and printers are already ready.
AWS Elastic Beanstalk is a good example of PaaS.
---
SaaS — Ordering Coffee at a Cafe
SaaS (Software as a Service) is software you use right away without installing or managing anything. Just open a browser and go.
The cafe selects the beans, roasts them, and brews the coffee — you just drink it. Gmail and Google Docs are everyday examples of SaaS.
!IaaS, PaaS, and SaaS compared
Management Responsibility Comparison
| Model | You Manage | Provider Manages | |-------|-----------|-----------------| | IaaS | OS, apps, data | Servers, networking, virtualization | | PaaS | App code, data | OS, runtime, infrastructure | | SaaS | Data, access settings | Everything else |
As you move from IaaS to SaaS, the amount you have to manage decreases.
---
Deployment Models — Public, Private, Hybrid
There are three ways to deploy cloud services depending on where and how you run them.
Public cloud means services like AWS, Azure, and GCP run on shared infrastructure used by many customers. This is the most common model.
Private cloud is a dedicated cloud environment for a single organization. It is used where security or regulatory requirements are very strict.
Hybrid cloud combines your own data center (on-premises) with a public cloud. For example, a hospital might keep patient records on its own servers while running its website on AWS. This is common in industries like healthcare and finance.
Multi-cloud means using multiple public clouds at the same time, such as AWS and Azure together. Do not confuse this with hybrid cloud.
---
Core Cloud Characteristics
These properties are what make cloud computing different from traditional IT. They appear frequently on the exam.
Elasticity means the system automatically adds servers when traffic increases and removes them when it drops. On Black Friday, a shopping site might see traffic jump 10 times. On-premises, you would have to buy enough hardware for that peak. With the cloud, you only pay for what you actually use.
Agility means being able to try new ideas quickly. Setting up a new server on-premises can take weeks. On AWS, it takes minutes.
High Availability means spreading your system across multiple data centers so that if one fails, the service keeps running from another.
Fault Tolerance goes one step further — zero downtime, even during a failure. High availability allows brief interruptions; fault tolerance allows none at all.
The shift from CapEx to OpEx means instead of large upfront investments to buy servers (capital expenditure), you pay monthly based on what you actually use (operating expenditure). This gives businesses much more financial flexibility from day one.
---
Exam Key Points
When you see these phrases, connect them to the right concept immediately.
"Automatically scales up and down based on demand" -- Elasticity
"Quickly provision, test, and deploy" -- Agility
"Keeps running without interruption" -- High Availability / "Absolutely zero downtime" -- Fault Tolerance
"Manage the OS yourself" -- IaaS / "Just deploy code" -- PaaS / "Use it in a browser" -- SaaS
"On-premises plus cloud at the same time" -- Hybrid Cloud
"No upfront investment, pay for what you use" -- CapEx to OpEx shift
"Create resources instantly without human involvement" -- On-demand self-service
The two most frequently tested topics are elasticity and the distinction between IaaS, PaaS, and SaaS. Lock in the keyword connections above and you will answer these questions quickly.