Cloud Computing · Terminology
Cloud Computing Terminology Every Beginner Should Learn
Quick summary — cloud computing terms for beginners
Core cloud computing terminology falls into four groups: service models such as IaaS, PaaS and SaaS; infrastructure terms such as regions, availability zones, VPCs and subnets; security terms such as IAM, roles and encryption; and scaling and cost terms such as autoscaling, load balancers, serverless and pay as you go.
In this guide you will learn:
- Service model terms — IaaS, PaaS and SaaS.
- Infrastructure terms — regions, zones, VPCs.
- Security terms — IAM, roles and encryption.
- Scaling and cost terms — with examples.
- Interview questions — that test cloud vocabulary.
SECTION 01Service models and core concepts
The first cloud terms most learners meet describe how much of the technology stack the cloud provider manages for you. With IaaS you manage more yourself; with SaaS you simply use finished software. Understanding these models helps you read job descriptions and choose the right service for a task. These are the foundation terms: Many beginners skip this step and jump straight into the console, which makes later topics such as security and pricing harder to follow. Spend a little time here first.
| Term | Plain English meaning | Example | You manage |
|---|---|---|---|
| IaaS | Rent virtual servers, storage and networks | Virtual machines such as EC2 | Operating system, apps, data |
| PaaS | A platform that runs your code for you | Managed app platforms, managed databases | Your code and data |
| SaaS | Finished software used over the internet | Email or office suites in the browser | Only your usage and settings |
| Shared responsibility | Provider secures the cloud; you secure what you put in it | You configure access and encryption | Your configuration |
LAYER IaaS PaaS SaaS
Application You You Provider
Data You You You (your content)
Runtime You Provider Provider
Operating system You Provider Provider
Virtual servers Provider Provider Provider
Physical hardware Provider Provider Provider
#!/usr/bin/env bash
# Configure the AWS CLI and run read-only commands (your practice account)
aws configure # access key, region (e.g. ap-south-1)
aws sts get-caller-identity # who am I?
aws ec2 describe-regions --output table | head -15
aws ec2 describe-availability-zones --region ap-south-1 \
--query 'AvailabilityZones[].ZoneName' --output text
SECTION 02Infrastructure terms: regions, zones and networks
Cloud resources live in physical data centres around the world, grouped into regions and availability zones. Inside a region you build private networks with subnets and control traffic with firewall-like rules. These terms appear in almost every architecture diagram, so understanding them makes the rest of cloud learning much easier: Try drawing a small network on paper before building it, labelling each subnet as public or private and noting which zone it sits in.
| Term | Plain English meaning | Example | Why it matters |
|---|---|---|---|
| Region | A geographic area with cloud data centres | Mumbai region (ap-south-1) | Latency, cost and data location |
| Availability zone | Separate data centre group within a region | Two zones in one region | Survive one zone failing |
| VPC and subnet | Your private network and its smaller sections | Public subnet for load balancer, private for database | Control what is exposed |
| Security group | Firewall rules attached to resources | Allow port 443 from the internet | Only needed traffic gets in |
import ipaddress
vpc = ipaddress.ip_network("10.0.0.0/16")
print("VPC addresses:", vpc.num_addresses)
subnets = list(vpc.subnets(new_prefix=24))[:4]
for name, net in zip(["public-a", "public-b", "private-a", "private-b"], subnets):
print(f"{name:10} {net} ({net.num_addresses} addresses)")
resource "aws_vpc" "main" {
cidr_block = "10.0.0.0/16"
tags = { Name = "learning-vpc" }
}
resource "aws_subnet" "public_a" {
vpc_id = aws_vpc.main.id
cidr_block = "10.0.0.0/24"
availability_zone = "ap-south-1a"
map_public_ip_on_launch = true
}
resource "aws_subnet" "private_a" {
vpc_id = aws_vpc.main.id
cidr_block = "10.0.2.0/24"
availability_zone = "ap-south-1a"
}
SECTION 03Security, scaling and cost terms
Once you can build resources, you need to control who can use them, help them handle changing traffic and keep costs under control. Security terms such as IAM and encryption, scaling terms such as autoscaling and load balancing, and cost terms such as pay as you go and reserved capacity appear in most cloud job descriptions and interviews: Beginners who learn these terms early tend to build safer, cheaper practice labs, because they think about access and spending from the first day.
| Term | Plain English meaning | Example | Group |
|---|---|---|---|
| IAM, role, policy | Who can do what; a set of permissions; the written rules | EC2 role that can read one bucket | Security |
| Encryption at rest / in transit | Protecting stored data / data moving over networks | Encrypted disks; HTTPS | Security |
| Load balancer and autoscaling | Spreads traffic; adds or removes servers with demand | More servers during a sale | Scaling |
| Serverless and pay as you go | Run code without managing servers; pay for what you use | Function that runs on each upload | Scaling and cost |
{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Action": ["s3:GetObject"],
"Resource": "arn:aws:s3:::learning-reports-bucket/*"
}
]
}
# AWS Lambda handler (Python runtime): runs when a file is uploaded to S3
import json
def lambda_handler(event, context):
records = event.get("Records", [])
for r in records:
bucket = r["s3"]["bucket"]["name"]
key = r["s3"]["object"]["key"]
print(f"new upload: s3://{bucket}/{key}")
return {"statusCode": 200, "body": json.dumps({"processed": len(records)})}
# Local test with a fake event:
if __name__ == "__main__":
fake = {"Records": [{"s3": {"bucket": {"name": "demo"}, "object": {"key": "a.csv"}}}]}
print(lambda_handler(fake, None))
SECTION 04Cloud glossary templates
Build your own cloud glossary using these templates:
Term: Availability zone
Plain meaning: A separate group of data centres within a region
Example: Running servers in two zones in the Mumbai region
Why it matters: The app keeps working if one zone fails
Related: Region, high availability, load balancer
Models: IaaS, PaaS, SaaS, shared responsibility
Infra: region, availability zone, VPC, subnet, security group
Security: IAM, role, policy, encryption, MFA
Scale/cost: load balancer, autoscaling, serverless, pay as you go,
reserved capacity, billing alarm, tagging
Explain each in one sentence, without notes:
1. IaaS vs PaaS vs SaaS
2. Region vs availability zone
3. Public vs private subnet
4. IAM role vs IAM user
5. Why autoscaling saves money
6. What the shared responsibility model means
SECTION 05Tips for learning cloud terminology
These habits help cloud vocabulary stick:
- Draw diagrams — sketch regions, zones, VPCs and subnets.
- Link terms to services — VPC, EC2 and S3 make concepts concrete.
- Use a practice account safely — set a billing alarm first.
- Explain simply — if you can explain it to a friend, you know it.
- Revise weekly — test yourself on your glossary.
SECTION 06Interview Q&A — cloud terms
Q1What is the difference between IaaS, PaaS and SaaS?
IaaS provides virtual infrastructure you manage, PaaS provides a platform that runs your code, and SaaS provides complete software you simply use.
Q2What is the difference between a region and an availability zone?
A region is a geographic area. Availability zones are separate data centre groups within a region, used to build fault-tolerant systems.
Q3What is a VPC?
A logically isolated private network in the cloud where you define IP ranges, subnets, routing and access rules.
Q4What is the shared responsibility model?
The provider secures the underlying infrastructure; the customer secures their data, configuration, access and applications.
Q5What does serverless mean?
Running code without managing servers; the provider handles scaling and infrastructure, and you typically pay per use.
SECTION 07Test yourself — cloud terms quiz
Five questions. No sign-up.
0 / 5Pick an answer to see why it is right or wrong.
SECTION 08Frequently asked questions
Which cloud terms should beginners learn first?
IaaS, PaaS, SaaS, region, availability zone, VPC, subnet, security group, IAM, encryption, load balancer, autoscaling, serverless and pay as you go.
What is cloud computing in simple words?
Using computing resources such as servers, storage and databases over the internet from a provider, paying for what you use instead of owning hardware. The provider looks after the physical hardware and data centres, while you decide what to build and how to configure it.
Are cloud terms the same across AWS, Azure and Google Cloud?
The concepts are the same, but service names differ. For example, a VPC on AWS is a VNet on Azure.
Do I need networking knowledge for cloud computing?
Yes, basic networking such as IP addresses, CIDR ranges, ports and DNS helps a lot with cloud design and troubleshooting.
How can I practise cloud terminology safely?
Use a free-tier practice account with a billing alarm, build small labs, draw diagrams and destroy resources after each session.
SECTION 09Related reads
Classroom & online · Noida
Learn cloud computing hands-on
Our AWS Training Course covers AWS fundamentals, networking, IAM, scaling and Terraform with guided hands-on labs.
Talk to a counsellor for current fees- Hands-on AWS labs
- Networking and IAM
- Terraform basics
- Weekday & weekend batches