IP Addressing Fundamentals Explained | Classes, CIDR & AWS VPC Networking

When I first started learning AWS networking and VPCs, the part that confused me the most was IP addressing.

Things like:

• CIDR ranges,
• subnet sizes,
• overlapping IPs,
• public vs private addressing,

all looked complicated initially.

But once I understood the basics behind IP classes and CIDR notation, VPC networking started making much more sense.

In this guide, I’ll break down the networking fundamentals covered in my video and explain how they relate to AWS VPC design in a practical way.

Why IP Addressing Matters in AWS

Every cloud infrastructure setup depends heavily on networking.

Before creating:

• VPCs,
• subnets,
• route tables,
• NAT gateways,
• or load balancers,

you need to understand how IP addressing works.

Otherwise it becomes very easy to:

• create overlapping networks,
• waste IP ranges,
• or design subnets incorrectly.

Understanding IPv4 Basics

IPv4 addresses use:

32 bits

and are usually written like:

192.168.1.118

Each section is called an octet.

IP Address Classes

Earlier networking models divided IP addresses into classes.

Although modern networking uses CIDR more heavily now, understanding classes still helps beginners visualize IP ranges better.

Class A

Range:

1.0.0.0 – 126.255.255.255

Class A networks are very large and support huge numbers of hosts.

Class B

Range:

128.0.0.0 – 191.255.255.255

Class B is medium-sized compared to Class A.

Class C

Range:

192.0.0.0 – 223.255.255.255

These are smaller networks commonly used in many local environments.

Classes D & E

These are reserved for:

• multicast
• research
• special networking purposes

and are not commonly used in standard VPC setups.

Public vs Private IP Addresses

One thing that becomes important in AWS is understanding:

• public IPs
• private IPs

Private IPs Inside Your Home

Inside most home networks:

• laptops
• phones
• TVs
• routers

all communicate using private IP addresses.

Example:

192.168.X.X

These IPs are not directly exposed to the internet.

Public IP Address

Your router usually communicates to the internet using:

One Public IP Address

This is how multiple local devices share internet connectivity.

Understanding this concept helps a lot later while designing:

• public subnets
• private subnets
• NAT architectures in AWS

CIDR Explained Simply

CIDR stands for:

Classless Inter-Domain Routing

This is one of the most important networking concepts in AWS.

CIDR notation defines:

• how large a network is
• how many IP addresses are available

CIDR Formula

The formula used is:

$2^{(32-\text{CIDR})}$2(32−CIDR)

This helps calculate the total number of IP addresses available.

Example: /16 CIDR

For:

/16

Available IPs:

$2^{(32-16)} = 2^{16} = 65536$2(32−16)=216=65536

That gives:

65,536 IP addresses

Example: /24 CIDR

For:

/24

Available IPs:

$2^{(32-24)} = 2^8 = 256$2(32−24)=28=256

That gives:

256 IP addresses

This is one of the most commonly used subnet sizes in AWS labs and projects.

Important AWS Networking Detail

One thing that confused me initially:

AWS reserves:

5 IP addresses

inside every subnet.

That means:

• a /24 subnet does NOT actually give 256 usable IPs.

Instead:

256 – 5 = 251 usable IPs

AWS reserves:

• first four IPs
• last IP

for internal networking purposes.

This is a very important detail beginners often miss.

Why CIDR Planning Matters

Poor CIDR planning can create major problems later.

Especially:

• overlapping VPCs
• overlapping subnets
• peering failures
• VPN routing conflicts

Once infrastructure grows, fixing bad network design becomes painful.

Overlapping IP Example

Example problem:

VPC 1

10.0.0.0/16

VPC 2

10.0.0.0/16

• VPC peering becomes problematic
• routing conflicts happen

This is why network planning matters early.

Practical AWS Demonstration

In the video, I also demonstrated:

• creating a VPC
• creating subnets
• CIDR assignments
• subnet planning

inside the AWS Console.

Actually seeing subnet creation visually makes the concepts much easier to understand compared to only reading definitions.

What Helped Me Understand Networking Better

Initially, networking looked extremely theoretical to me.

But once I started:

• building VPCs,
• creating subnets,
• troubleshooting routes,
• and working on VPN setups,

the concepts became much clearer.

Hands-on practice makes a huge difference.

Common Beginner Mistakes

Some very common networking mistakes include:

• overlapping CIDR blocks
• choosing subnets too small
• exposing private resources publicly
• misunderstanding public/private IP behavior
• incorrect route table setup

Almost everyone learning AWS networking runs into these at some point.

Full Video Walkthrough

I also created a complete walkthrough covering:

• IPv4 classes
• CIDR notation
• subnet calculations
• AWS reserved IPs
• VPC subnet creation
• public vs private networking
• avoiding overlapping CIDR ranges

along with practical AWS console demonstrations.

👉 Watch the full walkthrough here:

Why Networking Fundamentals Matter

Many AWS services eventually depend on networking:

• EC2
• RDS
• Load Balancers
• Kubernetes
• VPNs
• VPC Peering

Without networking fundamentals, cloud architecture becomes confusing very quickly.

Final Thoughts

Networking concepts can feel intimidating initially, especially CIDR calculations and subnet planning.

But once you:

• build VPCs,
• create subnets,
• and troubleshoot connectivity,

the concepts become much easier to understand.

In my experience, practical networking projects teach much more than memorizing theory alone.

What You Should Learn Next

After understanding CIDR and subnetting, explore:

• Route Tables
• Internet Gateway
• NAT Gateway
• Security Groups
• NACLs
• VPC Peering
• VPN architectures

Those concepts become much easier once IP addressing fundamentals are clear.

👉 Bonus Tip

When learning AWS networking:

• always draw architectures,
• plan CIDR ranges early,
• and avoid overlapping networks from the beginning.

That saves a lot of trouble later.

Related Guides

If you’re learning AWS and DevOps, also check:

• AWS OpenVPN + VPC Peering
• AWS Auto Scaling Explained
• AWS WAF Explained
• S3 + CloudFront Setup
• WordPress on AWS with ALB & SSL

About the Author

Madhukar Reddy is a DevOps engineer focused on AWS, Docker, Kubernetes, cloud infrastructure, and cyber security. He shares practical cloud and DevOps content based on hands-on deployments, networking projects, infrastructure troubleshooting, and real-world learning experiences.