Author Himanshu Bhatt documents his Networking for DevOps journey in the sixth entry of a public learning series. He breaks down why networks are split into subnets, explains the role of VPCs on AWS, GCP and Azure, and outlines the security and scaling benefits of isolating IP ranges.

He demystifies CIDR notation, showing that a /24 block yields roughly 256 addresses while larger prefixes expand the pool. The post warns that choosing a subnet too small can exhaust IPs, and stresses that public subnets host load balancers or bastion hosts, whereas private subnets keep app servers and databases hidden.

The guide introduces NAT gateways as the bridge that lets resources in private subnets reach the internet without exposing their private IPs. By translating outbound traffic to a public address, NAT preserves security while enabling updates and API calls. Misconfigured subnets or missing NAT remain the most common cloud networking headaches.