How cloud service models and virtual private networks use subnets, routes, gateways, policy boundaries, and controlled connectivity.
A virtual private cloud (VPC) is a logically isolated network environment in a cloud provider. It still requires subnets, route tables, gateways, address planning, and traffic policy; virtualization changes the implementation, not the need for network design.
| Concept | What it describes |
|---|---|
| IaaS, PaaS, SaaS | How responsibilities are divided between provider and customer |
| Public, private, hybrid, multicloud | Where workloads run and how environments are combined |
| VPC or virtual network | Logical network boundary within a provider |
| Subnet | Address range and routing scope within a virtual network |
| Gateway | Controlled connection to another network or service |
| Security group or equivalent | Provider policy applied to permitted traffic |
Cloud networks should use explicit routes and least-privilege traffic rules. Treat provider terminology as implementation-specific even when the underlying networking purpose is shared.