Skip to main content

Networking Glossary

Introduction​

Networking is the connective tissue of every cloud architecture. Before you can place a virtual machine, configure a database, or expose an API, you need a network to contain it. That makes networking vocabulary one of the first things any cloud learner must absorb — and one of the easiest places to get lost.

This Networking glossary section exists to give you clear, architecture‑aware definitions of the terms that matter most: VPC, VNet, subnet, CIDR, DNS, load balancer, NAT gateway, peering, transit, VPN, ExpressRoute, and more. Each entry explains what the concept means, where it fits in a cloud networking design, and how it relates to other networking building blocks.

Because CloudComputingDevPro is vendor‑aware but concept‑first, the glossary covers terms that appear across AWS, Azure, and GCP without assuming you work in only one. When provider terminology differs in ways that affect design — like VPC versus VNet — the entries make those differences explicit. The goal is to help you build a mental model of cloud networking that transfers cleanly across platforms.

Why Cloud Networking Vocabulary Matters​

Cloud networking is not just a set of standalone features. It’s a system where every concept depends on the others. A VPC doesn’t mean much without subnets; subnets don’t make sense without CIDR; a NAT gateway exists to solve a specific connectivity problem that arises from the split between public and private subnets. If you learn each term in isolation, the picture never comes together.

Provider naming adds another layer of complexity. A “VPC” in AWS and a “VNet” in Azure serve the same architectural role as an isolated private network, but they differ in how they relate to regions, subscriptions, and peering defaults. A “VPN gateway” exists in every major cloud, but its configuration model and high‑availability behavior vary. Without a shared vocabulary and a clear understanding of the underlying concepts, moving between providers — or even reading documentation — becomes harder than it needs to be.

This glossary section is built to solve that problem. It gives you the precise terminology, the relationships between terms, and the provider‑aware context that real engineering work requires. Whether you’re designing a landing zone, studying for an architecture certification, or troubleshooting connectivity, a solid networking vocabulary is the table stakes.

What You’ll Find in This Networking Glossary​

The glossary entries in this section cover cloud networking from the foundational virtual network boundary all the way through hybrid connectivity. They’re organized around a few natural groups:

  • Private network boundaries — the virtual networks that isolate your cloud resources from other tenants and from the public internet.
  • IP addressing and subnetting — how address space is carved up and assigned to workloads.
  • Public vs private connectivity — the mechanisms that control which resources can reach the internet and which cannot.
  • Traffic distribution and egress — how traffic enters, leaves, and moves through your cloud networks.
  • Internal connectivity between cloud networks — peering, transit, and hub‑and‑spoke patterns.
  • Hybrid and on‑premises connectivity — VPN, dedicated connections, and the terminology that describes enterprise network extension into the cloud.

Every entry focuses on core concepts and architectural role, not on step‑by‑step console instructions. You’ll understand what a NAT gateway is, why it exists, and how it differs from an internet gateway — not just which menu to click.

Explore Networking Concepts by Theme​

Private Network Boundaries​

The starting point for cloud networking is the virtual network: a logically isolated section of the cloud where you define your own IP address space and deploy resources. In AWS, this is called a VPC (Virtual Private Cloud). In Azure, it’s a VNet (Virtual Network). In GCP, it’s simply a VPC network, but with global‑by‑default behavior that differs from the regional model of the other two.

Understanding the boundaries of your private network is the first step toward designing security groups, network ACLs, subnets, and routing. The glossary entries in this group explain the purpose and architecture of these constructs, including how they map to regions, accounts, and subscriptions.

Subnets, CIDR, and IP Addressing​

Once you have a virtual network, you need to divide it. Subnets partition your address space into smaller ranges, letting you group resources by function, security requirements, or availability zone. CIDR (Classless Inter‑Domain Routing) notation is how you express those ranges, and it’s a fundamental skill for any engineer touching cloud networking.

This group covers subnet design, the difference between private and public IP addresses, and the IP planning considerations that arise when you’re building multi‑tier applications, connecting to on‑premises networks, or designing for future growth. The entries are practical: they teach you what a CIDR block looks like, why overlapping ranges are dangerous, and how to think about address space as a finite resource.

Name Resolution and Traffic Entry Points​

Applications and users need a way to find your services. DNS provides name resolution, translating human‑readable names into IP addresses within your virtual network and across the internet. Load balancers sit at the entry point of your application, distributing traffic across multiple instances for availability and scale.

The glossary explains what a load balancer does at the architectural level — how it differs from a reverse proxy, what layer it operates at, and why it’s a core building block for high availability. DNS entries cover resolution within cloud networks, public hosted zones, and the intersection of cloud DNS with your own domain management.

Egress and Outbound Connectivity​

Not every resource in a private subnet should be reachable from the internet, but many still need to initiate outbound connections — to download patches, call external APIs, or send data to a third‑party service. NAT gateways solve this problem by allowing outbound traffic from private subnets while blocking inbound connections initiated from the outside.

The glossary clarifies how NAT gateways work, why they’re deployed in public subnets despite serving private ones, and how they differ from internet gateways and NAT instances. Understanding egress is essential for any architecture that balances security with operational practicality.

Connectivity Between Cloud Networks​

As cloud environments grow, you often end up with multiple virtual networks — different teams, different applications, different accounts. Connecting them securely becomes an architecture question in itself. VPC peering and VNet peering provide direct, low‑latency connections between two networks. Transit gateways and similar hub‑and‑spoke models offer a more scalable pattern when you have many networks that all need to communicate.

These entries explain the difference between point‑to‑point peering and a transit architecture, the limitations of each, and why hub‑and‑spoke has become the default for enterprise cloud networking. You’ll find the conceptual foundation that makes provider‑specific documentation much easier to parse.

Hybrid and Dedicated Connectivity​

Most organizations don’t start from scratch in the cloud. They have data centers, branch offices, and existing WAN links that need to connect securely to cloud resources. VPN gateways provide encrypted tunnels over the public internet; ExpressRoute (Azure), Direct Connect (AWS), and Cloud Interconnect (GCP) offer dedicated, private connections with higher bandwidth and lower latency.

The glossary covers what these technologies are, how they differ in terms of SLA, latency, and encryption, and where hybrid connectivity fits into a broader networking architecture. These entries help you understand the trade‑offs without diving into a specific provider’s configuration guide.

Core Networking Terms You’ll See in This Section​

Within the Networking glossary, you’ll encounter a set of terms that form the backbone of cloud networking vocabulary. A VPC or VNet defines the private address space that everything else lives inside. Subnets carve that space into smaller, manageable segments, each assigned a CIDR block that determines its IP range. Within those subnets, resources receive private IP addresses for internal communication and, optionally, public IP addresses for internet reachability.

DNS translates names to addresses so that your applications don’t depend on hard‑coded IPs. Load balancers distribute incoming traffic across multiple compute instances, providing a single entry point and absorbing instance failures. NAT gateways let private resources reach the internet without being reachable themselves — a common pattern for patching, external API calls, and container image pulls.

When you need network‑to‑network communication within the cloud, VPC peering and VNet peering connect two virtual networks directly. Transit gateways scale that model to many networks, centralizing connectivity and reducing the mesh of pairwise connections. For hybrid scenarios, VPN gateways build encrypted tunnels over the public internet, while ExpressRoute, Direct Connect, and Cloud Interconnect offer private, dedicated links. Together, these terms describe the full spectrum of cloud networking from a single subnet to a global, multi‑region enterprise design.

How to Use This Networking Glossary​

This section is designed to support different learning styles and needs.

  • Learning cloud networking from scratch. Start with private network boundaries (VPC, VNet) and IP addressing (subnet, CIDR), then move through egress, load balancing, and internal connectivity. The entries build on each other naturally.
  • Clarifying a specific term while studying. If you’re reading AWS, Azure, or GCP documentation and hit an unfamiliar networking concept, jump directly to the relevant entry. Each page is self‑contained and links to related terms.
  • Building a foundation before deeper study. Before you tackle a networking guide like “How Cloud Networking Works” or an architecture article on network design, skim the key entries to make sure the vocabulary is solid.
  • Resolving confusion between similar concepts. If you’re unsure about the difference between a NAT gateway and an internet gateway, or between peering and transit, the glossary provides clean distinctions — and the Comparisons section goes deeper where needed.
  • Certification preparation. Cloud networking questions appear on every major architecture and administrator exam. The glossary gives you the conceptual clarity that helps you interpret scenario‑based questions accurately.

Networking Glossary vs Guides vs Architecture vs Comparisons​

CloudComputingDevPro organizes networking content across four layers that work together:

  • Glossary pages define a single networking concept in depth — what a VPC is, how a NAT gateway functions, what peering means.
  • Comparison pages draw the line between two related networking concepts — VPC vs VNet, public IP vs private IP, peering vs transit gateway, VPN vs ExpressRoute.
  • Guide pages connect multiple networking concepts into a system explanation — a guide like “How Cloud Networking Works” ties together VPC, subnets, routing, load balancers, and NAT into a coherent traffic‑flow picture.
  • Architecture pages apply networking concepts to design decisions — an article like “Cloud Networking Design Fundamentals” or “Hybrid Connectivity Architecture” shows how networking choices affect topology, resilience, security, and cost.

A typical learning path might look like this: you start with the glossary entry for VPC, then read the comparison page on VPC vs VNet when you encounter Azure, then work through a networking fundamentals guide that connects subnets, route tables, and load balancers, and finally study an architecture article on multi‑region networking that applies all of those pieces to a concrete design problem. The glossary is the entry point, but it’s designed to point you forward.

If you’re new to cloud networking, begin with these glossary entries:

  • VPC / VNet — understand the private network boundary first. Everything else lives inside it.
  • Subnet — learn how networks are segmented and why segmentation matters for security, availability, and traffic flow.
  • CIDR Block — get comfortable with IP address notation and range planning. It’s a foundational skill you’ll use in every design.
  • Load Balancer — see how traffic enters your application and how load balancers enable high availability and horizontal scaling.
  • NAT Gateway — grasp the difference between inbound and outbound connectivity and why private resources still need internet access.
  • VPN Gateway — understand the bridge between cloud and on‑premises, a requirement for almost every enterprise architecture.

Each of these terms unlocks a set of related concepts, and the glossary entries link onward so you can follow the threads as far as you need.

Certification-Oriented Learning​

Cloud networking is tested heavily in architecture and administrator certifications across AWS, Azure, and GCP. Questions often assume you already understand the meaning and role of VPC, subnet, CIDR, routing, NAT, load balancing, and hybrid connectivity — and that you can reason about how they interact under different scenarios.

The networking glossary helps you build that foundational understanding. When paired with networking guides and architecture articles, it gives you the conceptual depth that scenario‑based exam questions reward. For focused, exam‑style practice to complement this conceptual work, visit CloudCertPro.com.

FAQ​

What is included in a cloud networking glossary?
It covers private network boundaries (VPC, VNet), IP addressing and subnetting, DNS and load balancing, egress and NAT, internal connectivity (peering, transit), and hybrid connectivity (VPN, ExpressRoute, dedicated links). Every term is explained with its architectural role and provider‑aware context.

What cloud networking terms should beginners learn first?
Start with VPC/VNet, subnet, CIDR, load balancer, and NAT gateway. These five concepts form the core of most cloud networking designs and will unlock your understanding of more advanced topics.

Is a VPC the same as a VNet?
Architecturally, they serve the same purpose — an isolated virtual network — but they differ in regional scope, subscription/account association, and peering defaults. The glossary entries for each explain the differences in detail.

What is the difference between a subnet and a CIDR block?
A subnet is a segment of a virtual network where resources are placed. A CIDR block is the notation that defines its IP address range. The glossary explains how they relate and how to plan both.

Why do I need to understand NAT gateways and load balancers separately?
They serve completely different roles: a load balancer distributes incoming traffic to backend instances, while a NAT gateway enables outbound internet access for private resources. Confusing them can lead to design mistakes in traffic flow and security.

Does this section cover AWS, Azure, and GCP networking terminology?
Yes. The glossary is vendor‑aware and includes provider‑specific terminology when it differs meaningfully, while keeping the focus on the underlying networking concepts.

Should I start with networking glossary pages or networking guides?
If you’re encountering terms for the first time, start with the glossary. Once you have the vocabulary, move to a networking guide to see how the concepts fit together in a system. The two are designed to complement each other.

Can these networking glossary pages help with cloud certifications?
Absolutely. Networking questions appear on every cloud architecture and administration exam. A strong grasp of the terminology and relationships will make the exam content much more manageable.