Why CIDR blocks and IP addressing in AWS? - Purpose & Use Cases

The Big Idea

What if you could manage thousands of IP addresses as easily as one simple code?

The Scenario

Imagine you have a big box of addresses for your home deliveries, but you have to write down each address one by one to tell the delivery person where to go.

Now, think about managing hundreds or thousands of devices in a network, and you have to assign and track each IP address manually.

The Problem

Writing down or managing each IP address manually is slow and confusing.

It's easy to make mistakes like overlapping addresses or running out of space without realizing it.

This can cause devices to lose connection or create security risks.

The Solution

CIDR blocks let you group many IP addresses into neat, easy-to-manage chunks.

Instead of listing every address, you use a simple notation to represent a whole range.

This makes planning, assigning, and scaling networks much faster and safer.

Before vs After

✗ Before

Assign IPs one by one: 192.168.1.1, 192.168.1.2, 192.168.1.3 ...

✓ After

Use CIDR block: 192.168.1.0/24 to cover 256 addresses at once

What It Enables

With CIDR blocks, you can easily design and grow your network without worrying about address conflicts or wasted space.

Real Life Example

When setting up a company's cloud network, CIDR blocks help assign IP ranges to different departments, so their devices communicate smoothly and securely.

Key Takeaways

Manual IP management is slow and error-prone.

CIDR blocks simplify grouping and assigning IP addresses.

This helps build scalable and reliable networks easily.

Practice

1. What does a CIDR block like 192.168.1.0/24 represent in AWS networking?

easy

A. A single IP address 192.168.1.24

B. An invalid IP address range

C. A subnet mask of 255.255.0.0

D. A range of IP addresses from 192.168.1.0 to 192.168.1.255

Solution

1. Step 1: Understand CIDR notation

   The number after the slash (/24) shows how many bits are fixed for the network part. Here, 24 bits fixed means the first 3 parts (192.168.1) are fixed.

2. Step 2: Calculate the IP range

   With 24 bits fixed, the last 8 bits can vary from 0 to 255, so the range is 192.168.1.0 to 192.168.1.255.

3. Final Answer:

   A range of IP addresses from 192.168.1.0 to 192.168.1.255 -> Option D

4. Quick Check:

   CIDR /24 means 256 addresses [OK]

Hint: Count bits after slash to find IP range size [OK]

Common Mistakes:

• Confusing CIDR with a single IP
• Misreading the subnet mask bits
• Assuming /24 means only 24 addresses

2. Which of the following is the correct CIDR notation for a subnet with 512 IP addresses?

easy

A. /23

B. /25

C. /22

D. /24

Solution

1. Step 1: Calculate bits needed for 512 addresses

   512 addresses require 9 bits (2^9 = 512) for host part.

2. Step 2: Determine CIDR prefix

   IPv4 has 32 bits total, so prefix = 32 - 9 = 23. So CIDR is /23.

3. Final Answer:

   /23 -> Option A

4. Quick Check:

   512 IPs = 2^(32-23) = 512 [OK]

Hint: Use 32 minus log2(IP count) for CIDR [OK]

Common Mistakes:

• Choosing /24 which gives only 256 addresses
• Confusing /22 with 1024 addresses
• Miscounting bits for hosts

3. Given the CIDR block 10.0.0.0/26, how many usable IP addresses are available for hosts?

medium

A. 64

B. 62

C. 32

D. 30

Solution

1. Step 1: Calculate total IPs in /26 block

   /26 means 32 - 26 = 6 bits for hosts, so total IPs = 2^6 = 64.

2. Step 2: Subtract network and broadcast addresses

   Two addresses are reserved (network and broadcast), so usable IPs = 64 - 2 = 62.

3. Final Answer:

   62 -> Option B

4. Quick Check:

   Usable IPs = total - 2 [OK]

Hint: Usable IPs = 2^(32 - prefix) - 2 [OK]

Common Mistakes:

• Counting all IPs as usable
• Forgetting to subtract network and broadcast
• Mixing up prefix length and host bits

4. You have a VPC with CIDR block 172.16.0.0/16. You want to create two subnets without overlapping IPs. Which pair of CIDR blocks is valid?

medium

A. 172.16.0.0/17 and 172.16.128.0/17

B. 172.16.0.0/18 and 172.16.64.0/17

C. 172.16.0.0/16 and 172.16.0.0/17

D. 172.16.0.0/15 and 172.16.128.0/17

Solution

1. Step 1: Understand the VPC range

   172.16.0.0/16 covers IPs from 172.16.0.0 to 172.16.255.255.

2. Step 2: Check subnet ranges for overlap

   /17 splits the /16 into two halves: 172.16.0.0 to 172.16.127.255 and 172.16.128.0 to 172.16.255.255. These do not overlap.

3. Final Answer:

   172.16.0.0/17 and 172.16.128.0/17 -> Option A

4. Quick Check:

   Non-overlapping halves split /16 into two /17s [OK]

Hint: Split CIDR by increasing prefix to avoid overlap [OK]

Common Mistakes:

• Choosing overlapping CIDRs
• Using larger CIDR than VPC block
• Ignoring subnet mask sizes

5. You need to design a VPC with exactly 3 subnets: one public with 100 IPs, one private with 50 IPs, and one isolated with 25 IPs. Which CIDR block allocation fits best inside 10.0.0.0/24 without overlap?

hard

A. 10.0.0.0/24, 10.0.1.0/25, 10.0.2.0/26

B. 10.0.0.0/26, 10.0.0.64/26, 10.0.0.128/26

C. 10.0.0.0/25, 10.0.0.128/26, 10.0.0.192/27

D. 10.0.0.0/26, 10.0.0.64/27, 10.0.0.96/28

Solution

1. Step 1: Calculate needed CIDR for each subnet

   100 IPs need at least /25 (128 IPs), 50 IPs need /26 (64 IPs), 25 IPs need /27 (32 IPs).

2. Step 2: Assign CIDRs inside 10.0.0.0/24 without overlap

   10.0.0.0/25 covers 0-127, 10.0.0.128/26 covers 128-191, 10.0.0.192/27 covers 192-223. These fit perfectly without overlap.

3. Final Answer:

   10.0.0.0/25, 10.0.0.128/26, 10.0.0.192/27 -> Option C

4. Quick Check:

   Subnet sizes fit and sum within /24 [OK]

Hint: Match subnet size to nearest CIDR block, assign sequentially [OK]

Common Mistakes:

• Using CIDRs too small for IP needs
• Overlapping subnet ranges
• Assigning subnets outside VPC CIDR