Cloud Computing Glossary

Introduction

The CloudComputingDevPro glossary is a practical, structured library of cloud computing concepts — not a list of short definitions.

Cloud documentation is full of terms that sound similar but describe very different things: an Availability Zone is not the same as a region; disaster recovery is not the same as high availability; a VPC and a VNet serve similar roles but have different design constraints. If you only learn the vocabulary, you miss the architecture thinking that turns words into working systems.

This glossary is built for engineers and architects who want to understand cloud terms in context. Each entry explains what a concept means, where it fits in cloud architecture, how it relates to other concepts, and — when it helps — how it maps across AWS, Azure, and GCP. It’s reference material you can use while reading documentation, and it’s also a structured way to build foundational cloud knowledge from the ground up.

Whether you’re a developer moving into cloud engineering, an architect expanding across providers, or a certification learner who wants to understand concepts rather than memorize factoids, the glossary is designed to meet you where you are.

What This Cloud Glossary Covers

The glossary spans the full breadth of cloud computing, organized by architectural domains rather than alphabetical order. You’ll find deep coverage of networking, security, compute, storage, and databases, alongside dedicated sections for DevOps, containers, serverless, observability, governance, AI, and migration. Architecture and resilience concepts — like high availability, disaster recovery, RPO, RTO, and landing zones — form the backbone that connects all the other domains.

This structure reflects how cloud systems are actually built. Networking and security aren’t separate disciplines bolted on at the end; they’re inseparable from compute design, observability, and governance. By grouping terms this way, the glossary helps you see the relationships between concepts rather than treating them as a pile of independent vocabulary.

Explore the Glossary by Topic

Foundation

Cloud foundation defines the structure of everything you build. The foundation glossary covers foundational concepts like regions, Availability Zones, fault domains, and update domains — the physical and logical building blocks of cloud platforms. It also covers resilience concepts that guide design decisions: high availability, fault tolerance, disaster recovery, RPO, RTO, and the shared responsibility model.

These terms aren’t abstract. When you understand how an Availability Zone relates to a region and to fault tolerance, you can reason about instance placement, multi-AZ database configuration, and the real meaning of an SLA. The foundation glossary lays that foundation.

Explore the foundation glossary to learn more.

Networking

Networking is the connective tissue of cloud infrastructure. The networking glossary covers virtual networks (VPC, VNet), IP addressing (CIDR, private IP, public IP), DNS, subnets, and the services that control traffic flow: load balancers, NAT gateways, and firewalls. It also covers connectivity patterns like VPC peering, VNet peering, transit gateways, VPN Gateway, ExpressRoute, and cloud interconnect.

These terms are explained with an eye toward how they work together in a design — for example, how subnet design interacts with load balancer placement, or how peering and transit gateways solve different problems. When it’s useful, the glossary highlights the provider-specific terminology and behavior that can trip up engineers working across clouds.

Explore the networking glossary to learn more.

Security

Security in the cloud is a design discipline, not a feature checklist. The security glossary covers identity and access management (IAM, RBAC, least privilege, managed identities, service accounts), authentication and authorization (MFA, conditional access), encryption (at rest, in transit, customer-managed keys), and secrets management. It also covers architectural concepts like zero trust and the shared responsibility model.

These entries explain both what each term means and why it matters in practice. For example, understanding the difference between an IAM role and an IAM policy changes how you design permission boundaries. Knowing how managed identities work in different clouds helps you avoid long-lived credentials.

Compute

The compute glossary focuses on the models and scaling behaviors that determine how workloads run. Horizontal scaling, vertical scaling, auto-scaling, and elasticity are core concepts, but the section also covers instance types, capacity planning, and the trade‑offs between different compute models (virtual machines, containers, serverless).

These terms are explained in the context of availability and cost — because a scaling decision is rarely just about performance. The compute glossary gives you the vocabulary and reasoning to choose the right model for a given workload.

Storage

Cloud storage is more than just “file storage.” The storage glossary covers block storage, object storage, file storage, and their cloud-specific implementations (EBS, S3, Azure Blob, Managed Disks, Filestore). It also covers durability, availability, replication, snapshots, and backup strategies.

Each entry connects storage concepts to architecture decisions: when object storage works better than block, what consistency models mean for application design, and how storage durability interacts with disaster recovery planning.

Database

The database glossary covers relational databases, NoSQL databases, managed database services, caching layers, and the data modeling implications that come with each choice. Topics include read replicas, failover, sharding, partitioning, and consistency models.

These entries treat databases as an integral part of cloud architecture, not a separate silo. They explain how database design decisions ripple into application performance, resilience, and cost.

DevOps

The DevOps glossary covers the practices and tooling that connect development and operations in cloud environments. Infrastructure as Code, continuous integration, continuous delivery, immutable infrastructure, and configuration management are central topics.

The glossary explains these concepts in terms that make sense for cloud engineers: how IaC changes the way you think about provisioning, what it means to treat infrastructure as immutable, and why CI/CD pipelines are a first-class concern in cloud-native operations.

Containers

Containers have become a standard packaging and runtime model in modern cloud workloads. The containers glossary covers Docker, Kubernetes, container orchestration, pod networking, service meshes, and container registries.

These entries don’t assume you already know Kubernetes internals. They explain the fundamentals — what a container is, why orchestration exists, how a service mesh differs from a load balancer — so you can approach container platforms with a clear architectural picture.

Serverless

Serverless computing changes the runtime model, but it doesn’t eliminate the need for architecture thinking. The serverless glossary covers functions (AWS Lambda, Azure Functions), event-driven architectures, serverless databases, and the operational trade‑offs that come with fully managed execution environments.

Entries explain what “serverless” really means, how cold starts affect design, and how to think about observability and security in event‑driven systems.

Observability

Observability is about understanding system behavior from the outside. The observability glossary covers the three pillars — monitoring, logging, and distributed tracing — and goes further into concepts like SLIs, SLOs, error budgets, and alerting.

These entries draw a clear line between “having dashboards” and building an observable system. They explain how logging and tracing serve different purposes, and why observability is as much an architectural concern as it is an operational one.

Governance

Cloud governance keeps growth manageable. The governance glossary covers policy, compliance, resource tagging, cost management, organization structures, and the governance aspects of landing zones.

These terms are explained in the context of multi-account and multi-subscription environments — the kinds of setups where governance isn’t optional.

AI

The AI glossary covers the fundamental terms of artificial intelligence and machine learning in the cloud: training, inference, model deployment, feature stores, and MLOps. It also maps major cloud AI services (SageMaker, Azure Machine Learning, Vertex AI) at a conceptual level.

Entries are written for engineers who need to understand the ML infrastructure landscape without becoming data scientists.

Migration

The migration glossary covers the strategies, patterns, and terminology of moving workloads to the cloud: the 6 R’s (rehost, replatform, refactor, etc.), migration assessment, discovery tools, and cutover planning.

These terms help you talk about migration projects with a shared vocabulary and a realistic sense of the architectural effort involved.

How to Use This Glossary

This glossary is meant to support different ways of learning and working.

As a quick reference. When you encounter an unfamiliar term in a cloud documentation page, architecture diagram, or certification study guide, you can jump straight to the relevant entry. Each page is self-contained and includes links to related concepts so you can broaden your understanding without starting from scratch.

As a structured learning path. If you’re building cloud knowledge from the ground up, you can follow the glossary categories in a deliberate order — starting with architecture and networking fundamentals, moving through security and compute, and then into operations, observability, and more advanced topics. The recommended path below gives you a concrete starting point.

As a cross-cloud concept mapper. The glossary often compares how AWS, Azure, and GCP implement the same concept. This is especially useful if you’re already familiar with one provider and need to pick up another, or if you’re designing multi-cloud architectures and need clarity on where concepts align — and where they don’t.

As a certification study companion. Many cloud certification exams test conceptual understanding, not just feature knowledge. The glossary helps you build that understanding so that when you see a scenario question about high availability or IAM, you can reason from principles instead of relying on rote memory.

Recommended Learning Path

If you’re relatively new to cloud computing and want a structured way through the glossary, here’s a path that respects how concepts build on each other.

1. Architecture foundations. Start with region, Availability Zone, high availability, fault tolerance, disaster recovery, RPO, RTO, and the shared responsibility model. These terms describe the physical and logical landscape of every cloud platform.

2. Networking fundamentals. Move into VPC, VNet, subnet, CIDR, DNS, load balancer, and NAT gateway. Understanding how traffic flows and how networks are segmented is essential before tackling more complex designs.

3. Security essentials. Study IAM, RBAC, least privilege, managed identity, MFA, encryption at rest, encryption in transit, key management, and secrets management. Security is not an add‑on — it’s a layer that touches every other part of the system.

4. Compute and scaling. Understand horizontal scaling, vertical scaling, auto-scaling, and elasticity. Then explore how these concepts apply to VMs, containers, and serverless workloads.

5. DevOps and operations. Learn Infrastructure as Code, CI/CD, immutable infrastructure, monitoring, logging, and distributed tracing. These are the practices that keep cloud systems running and evolving safely.

6. Advanced and cross‑cutting topics. From here, you can branch into governance, migration, AI, or deepen your knowledge in any area relevant to your work.

This isn’t a rigid curriculum; it’s a sequence that minimizes the number of times you’ll encounter a term before its dependencies are clear.

AWS, Azure, and GCP Concept Mapping

One of the biggest challenges in cloud learning is that different providers use different names for similar ideas — and sometimes the ideas themselves aren’t identical.

Throughout the glossary, you’ll find entries that map concepts across AWS, Azure, and GCP. For example, an entry might explain that a VPC (AWS) and a VNet (Azure) serve the same architectural role as an isolated virtual network, but they differ in how they handle regional scope, peering defaults, and IP address management. Similarly, IAM roles in AWS and managed identities in Azure both provide temporary, non‑human credentials, but their lifecycle and scope behave differently.

This mapping is not about declaring “X equals Y.” It’s about giving you a clear, honest picture of how cloud platforms compare — so you can make accurate design decisions and avoid costly misunderstandings.

Beyond Definitions: Architecture Context Matters

Knowing what a term means is only the first step. Understanding how it connects to other concepts is what separates vocabulary from architectural judgment.

Consider high availability and disaster recovery. Both deal with keeping systems running, but they address different failure scopes and use different patterns. High availability is about surviving component failures within a region through redundancy and automatic failover. Disaster recovery is about surviving a regional outage through cross‑region replication and planned recovery procedures. Mixing them up leads to designs that meet neither goal.

Similarly, VPC, subnet, and load balancer are not independent — they form a traffic path. A subnet design that ignores load balancer placement can create unnecessary complexity and cost. IAM, least privilege, and key management are a security chain; weakening any one link changes the overall security posture. Observability isn’t just monitoring plus logging — it’s about being able to ask new questions of a system without shipping new code.

This glossary treats concepts as part of a larger system. Each entry links to related terms and points toward the architecture articles and comparisons that go deeper. The goal is to help you build a connected mental model of cloud architecture, not a collection of isolated facts.

Certification-Oriented Learning

Many readers use the glossary to build the conceptual foundation that architecture‑oriented certifications require. Exams like AWS Solutions Architect, Azure AZ‑305, or Google Cloud Professional Cloud Architect reward deep understanding, not surface‑level recall. The glossary helps you develop that understanding.

That said, this site does not provide practice exams or timed test simulations. If you’re actively preparing for a certification and want to measure your readiness with focused, exam‑style questions, we recommend continuing your practice on CloudCertPro.com. Think of the glossary as the place you build durable knowledge, and CloudCertPro as the place you validate it under test conditions.

FAQ

What is a cloud computing glossary?
It’s a structured collection of cloud terminology, but this one goes beyond short definitions. Each entry explains what a term means, how it fits into cloud architecture, how it relates to other concepts, and — when relevant — how it’s implemented across AWS, Azure, and GCP.

Is this glossary only for beginners?
No. While it’s accessible to newcomers, the architecture context and cross‑provider mappings make it useful for experienced engineers, architects, and anyone moving between cloud platforms or into senior roles.

Does the glossary cover AWS, Azure, and GCP?
Yes. It’s vendor‑aware and often includes provider‑specific notes and comparisons, but the primary focus is on concepts that apply across clouds. The glossary helps you understand both common ideas and the differences that matter.

What cloud topics should I learn first?
We recommend starting with architecture fundamentals (region, Availability Zone, high availability, disaster recovery, shared responsibility), then networking, security, and compute fundamentals. The Recommended Learning Path on this page gives a more detailed sequence.

How is this glossary different from a normal technical dictionary?
A dictionary gives you a definition. This glossary gives you definition, architecture context, relationships to other concepts, and cross‑cloud mapping. It’s designed to build understanding, not just answer “what does this word mean.”

Can this glossary help with cloud certifications?
Absolutely. Many certification questions test your ability to apply concepts in architecture scenarios. The glossary builds that conceptual depth. For exam‑focused practice, we recommend pairing it with resources like CloudCertPro.com.

What is the difference between architecture terms and service‑specific terms?
Architecture terms describe patterns and design principles (high availability, disaster recovery, RPO, RTO, landing zone, zero trust). Service‑specific terms describe cloud provider features (AWS Lambda, Azure Functions, Amazon S3). The glossary covers both, but it always connects service‑specific terms to the architectural concepts they implement.

Do glossary pages include design context or only definitions?
Design context is central. Every glossary entry includes architectural context — where the term fits, what it interacts with, and what trade‑offs it implies — so you can apply it in real design work, not just recognize it on a slide.