Cloud Computing · Glossary
Cloud Computing Glossary — 50 Terms You Must Know in 2026
Quick summary — cloud computing glossary
This cloud computing glossary explains 50 essential terms in four groups: foundations, compute and storage, networking and security, and advanced ideas. Start with service models, regions and availability zones, then learn instances, object storage and autoscaling, and finish with VPCs, IAM, encryption and infrastructure as code.
In this guide you will learn:
- Foundations — 14 terms on service models and global infrastructure.
- Compute and storage — 14 terms on servers, containers and data.
- Networking and security — 14 terms on VPCs, IAM and encryption.
- Advanced terms — 8 ideas to grow into.
- Study tips — making cloud vocabulary stick.
SECTION 01Foundations: cloud models and global infrastructure (14 terms)
These terms describe what the cloud is and how providers organise it. They appear in every introductory course and certification exam. The most important idea is the shared responsibility model: the provider secures the underlying infrastructure, and you are responsible for how you configure and use the services.
| Term | Plain meaning | Example | Why it matters |
|---|---|---|---|
| IaaS | Rent virtual servers, storage and networks | Amazon EC2 | You manage the OS and apps |
| PaaS | Platform runs your code; you skip server management | AWS Elastic Beanstalk | Faster deployment |
| SaaS | Complete software used over the internet | Email or CRM tools | No infrastructure to manage |
| Shared responsibility | Provider secures the cloud; you secure what you put in it | You configure IAM and data access | Most incidents are customer misconfigurations |
5. Public cloud Services offered over the internet to many customers
6. Private cloud Cloud-style infrastructure for one organisation
7. Hybrid cloud Mix of on-premises and public cloud
8. Multi-cloud Using more than one cloud provider
9. Region Geographic area with data centres (ap-south-1)
10. Availability Zone One or more isolated data centres in a region
11. Edge location Site that caches content close to users (CDN)
12. Pay-as-you-go Billing for what you use
13. Elasticity Scaling resources up or down with demand
14. High availability Design that keeps running when parts fail
# Which regions and AZs can I use?
aws ec2 describe-regions --query "Regions[].RegionName" --output table
aws ec2 describe-availability-zones --region ap-south-1 \
--query "AvailabilityZones[].ZoneName" --output text
# Who am I logged in as?
aws sts get-caller-identity
SECTION 02Compute and storage terms (14 terms)
Compute terms describe where your code runs, from full virtual machines to functions that run only when triggered. Storage terms describe how data is kept: as files, blocks attached to servers, or managed databases. Choosing the right type affects cost, performance and how much you have to manage yourself.
| Term | Plain meaning | Example | Why it matters |
|---|---|---|---|
| Instance | A virtual server | EC2 t3.micro | Basic unit of IaaS compute |
| Serverless | Run code without managing servers | AWS Lambda | Pay per execution |
| Object storage | Store files as objects with keys | Amazon S3 | Cheap, durable, scalable |
| Autoscaling | Automatically adjust number of servers | EC2 Auto Scaling group | Handles demand changes |
19. AMI / image Template used to launch servers
20. Container Packaged app with its dependencies (Docker)
21. Kubernetes System that runs and manages containers
22. Block storage Disk volumes attached to servers (EBS)
23. File storage Shared file system (EFS)
24. Managed database Database run by the provider (RDS)
25. Snapshot Point-in-time copy of a volume or database
26. Storage class Price/speed tier for objects (S3 Glacier)
27. Load balancer Spreads traffic across servers (ALB)
28. Spot instance Spare capacity at lower price, can be reclaimed
# Object storage: create a bucket and upload a file
aws s3 mb s3://yourname-glossary-demo-2026 --region ap-south-1
aws s3 cp notes.txt s3://yourname-glossary-demo-2026/
aws s3 ls s3://yourname-glossary-demo-2026/
# Serverless: invoke a function you created
aws lambda invoke --function-name hello-glossary out.json
cat out.json
SECTION 03Networking and security terms (14 terms)
Networking and security terms are where most beginners struggle, and where most real-world cloud problems happen. A VPC is your private network; subnets divide it; security groups and IAM policies control who and what can connect. Encryption and logging protect data and give you evidence when something goes wrong.
| Term | Plain meaning | Example | Why it matters |
|---|---|---|---|
| VPC | Your isolated private network in the cloud | 10.0.0.0/16 | Foundation of cloud networking |
| Subnet | A slice of a VPC's IP range | Public and private subnets | Separates internet-facing parts |
| IAM | Identity and Access Management | Users, roles, policies | Controls who can do what |
| Security group | Virtual firewall for resources | Allow port 443 from the internet | First line of network defence |
33. CIDR block IP range notation (10.0.1.0/24)
34. Internet gateway Connects a VPC to the internet
35. NAT gateway Lets private subnets reach out, not in
36. Route table Rules for where network traffic goes
37. IAM role Identity assumed by services or users
38. Policy JSON document granting permissions
39. MFA Multi-factor authentication
40. Encryption at rest Data encrypted on storage (KMS)
41. Encryption in transit Data encrypted on the network (TLS)
42. Audit log Record of API actions (CloudTrail)
{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Action": ["s3:GetObject"],
"Resource": "arn:aws:s3:::yourname-glossary-demo-2026/*"
}
]
}
SECTION 04Advanced cloud terms (8 terms)
You will meet these as you move from single labs to real production systems.
43. Infrastructure as Code (IaC)
Defining infrastructure in files (Terraform,
CloudFormation) so it is repeatable and reviewable.
44. Immutable infrastructure
Replacing servers with new ones instead of
changing them in place.
45. Blue-green deployment
Running two environments and switching traffic
to the new one after checks pass.
46. RPO (Recovery Point Objective)
Maximum acceptable data loss, measured in time.
47. RTO (Recovery Time Objective)
Maximum acceptable time to restore service.
48. FinOps
Practice of managing and optimising cloud costs
across engineering and finance teams.
49. Well-Architected Framework
Provider guidance on reliability, security,
performance, cost and operations (and
sustainability) for cloud designs.
50. Landing zone
A pre-configured multi-account setup with
security, networking and logging baselines.
SECTION 05Tips to learn cloud vocabulary
Cloud terms stick faster when you see them in a console or a command:
- Use the free tier carefully — create small resources, explore, then delete them.
- Draw a VPC by hand — subnets, gateways and route tables make sense once drawn.
- Read service FAQs — providers' FAQ pages explain terms in practical language.
- Set a billing alarm first — learning should never come with a surprise bill.
- Link terms to exam objectives — certification guides list exactly which terms matter.
SECTION 06Interview Q&A — cloud computing terms
Q1What is the difference between IaaS, PaaS and SaaS?
IaaS gives you virtual infrastructure to manage yourself, PaaS runs your application code while managing the platform, and SaaS is complete software you simply use. Responsibility shifts towards the provider from IaaS to SaaS.
Q2What is an Availability Zone?
An Availability Zone is one or more isolated data centres within a region, with independent power and networking. Spreading resources across zones improves availability.
Q3What is the shared responsibility model?
The cloud provider is responsible for securing the physical infrastructure and core services, while the customer is responsible for configuring access, data protection, networks and applications they deploy.
Q4What does a NAT gateway do?
It lets resources in private subnets make outbound connections to the internet, such as downloading updates, without allowing inbound connections from the internet.
Q5What is the difference between RPO and RTO?
RPO is how much data loss is acceptable, measured in time since the last good copy. RTO is how long it may take to restore the service after an outage.
SECTION 07Test yourself — cloud computing terms quiz
Five questions. No sign-up.
0 / 5Pick an answer to see why it is right or wrong.
SECTION 08Frequently asked questions
What are the basic terms in cloud computing?
Start with IaaS, PaaS, SaaS, public and private cloud, region, availability zone, instance, object storage, VPC, IAM and autoscaling. They appear in every beginner course.
What is the difference between a region and an availability zone?
A region is a geographic area such as Mumbai. An availability zone is an isolated data centre group within that region. Regions contain multiple zones.
What is serverless computing?
Serverless lets you run code or use services without managing servers. The provider handles scaling and infrastructure, and you typically pay per request or execution time.
Is cloud computing hard to learn for beginners?
The number of services can feel overwhelming, but the core concepts — compute, storage, networking and identity — are manageable. Learning a few services deeply first makes the rest easier.
Which cloud terms are most important for interviews?
Shared responsibility, regions and AZs, VPC and subnets, security groups, IAM roles and policies, autoscaling, load balancers, object storage and infrastructure as code.
SECTION 09Related reads
Classroom & online · Noida
Turn cloud vocabulary into hands-on skill
Our AWS Training Course covers core AWS services, networking, IAM, storage and automation through guided labs where every term in this glossary is used.
Talk to a counsellor for current fees- Guided AWS labs
- Networking and IAM practice
- Infrastructure as code basics
- Weekday & weekend batches