# IP Addressing

IP addressing is the system of assigning logical network addresses to interfaces so that devices and services can identify endpoints and route traffic between networks.

Cloud concept. Updated 2026-10-29. Page: https://blowstack.com/tools/cloud-concepts-hub/ip-addressing

> IP addresses identify network interfaces, while address ranges define how networks are divided and connected. In cloud environments, an addressing plan determines subnet capacity, private and internet connectivity, and whether networks can communicate without overlapping address ranges.

Practice exams covering IP Addressing: [ANS-C01 AWS Certified Advanced Networking - Specialty](https://blowstack.com/practice-exams/aws-certified-advanced-networking-specialty), [SOA-C03 AWS Certified CloudOps Engineer - Associate](https://blowstack.com/practice-exams/aws-certified-cloudops-engineer-associate), [SAA-C03 AWS Certified Solutions Architect - Associate](https://blowstack.com/practice-exams/aws-certified-solutions-architect-associate).

## 6 key aspects of IP Addressing

Effective IP addressing combines capacity planning, address scope, subnet organization, routing, and non-overlapping ranges to support reliable cloud connectivity.

1. **CIDR ranges and subnet capacity**: CIDR notation defines a network's address range and size. Calculate usable capacity after provider reservations and allow room for scaling, deployments, and managed-service network interfaces.
2. **Public and private address scope**: Private IPv4 addresses support private-network communication but are not publicly routed on the internet. Public addressing enables internet routing only when the required routes, gateways, and security controls are also present.
3. **VPC and subnet organization**: A VPC provides address space that is divided into non-overlapping subnet ranges. In AWS, each subnet belongs to one Availability Zone, so resilient applications typically need subnets in multiple zones.
4. **Routing and gateway behavior**: Route tables select where traffic goes; an IP address alone does not establish connectivity. Internet gateways, NAT gateways, and egress-only internet gateways support different connectivity patterns.
5. **IPv4 and IPv6 coexistence**: Dual-stack networks use both address families, each with its own addressing and routing requirements. IPv6 expands address capacity but does not replace the need for access controls.
6. **Non-overlapping address planning**: Allocate distinct ranges to networks that may need to connect through peering, VPNs, or other private connectivity. Overlap can block straightforward routing and require renumbering, translation, or a different connectivity design.

## Cloud services for IP Addressing

Amazon VPC defines address ranges, subnets, and routing paths, while EC2 consumes subnet addresses through network interfaces. Elastic Load Balancing provides application endpoints and distributes connections across targets, reducing clients' dependence on individual instance addresses. Route 53 connects readable names to these endpoints through DNS. Together, these services separate address allocation, network reachability, traffic distribution, and name resolution. Engineers must still coordinate subnet capacity, gateway routes, and security rules: a valid DNS response or an assigned IP address does not prove that an application is reachable.

- **[Amazon VPC](https://blowstack.com/tools/cloud-services-hub/amazon-vpc)**: Amazon VPC implements cloud network address spaces, subnets, route tables, and gateway connectivity. Its IP Address Manager capability helps allocate address ranges and monitor address usage across environments.
- **[Amazon EC2](https://blowstack.com/tools/cloud-services-hub/amazon-ec2)**: EC2 instances use network interfaces with private IP addresses from their subnets and can also use IPv6 addresses or public IPv4 connectivity. Elastic IP addresses provide static public IPv4 addresses that can be reassociated with supported resources.
- **[Amazon Route 53](https://blowstack.com/tools/cloud-services-hub/amazon-route-53)**: Route 53 provides DNS records that let clients locate endpoints without hard-coding IP addresses. Private hosted zones support name resolution within associated VPCs, while public hosted zones publish records through public DNS.

## IP Addressing exam questions

Real practice exam questions on IP Addressing, with the correct answer and its explanation.

### Question 1 (SOA-C03)

**Question:**

A CloudOps engineer is provisioning EC2 worker instances that require IPv4 prefix delegation. Each worker's network interface requests one Amazon-provided /28 IPv4 prefix. Deployment fails with an InsufficientCidrBlocks error in a /24 subnet.

The subnet has 80 available IPv4 addresses, but existing network interfaces occupy addresses in every /28-aligned block. These interfaces must retain their current addresses. The VPC has unused IPv4 address space, and the workers can use a new subnet in the same Availability Zone. All required permissions and service quotas are sufficient.

Which action will resolve the deployment failure?

**Correct answer:** Create an empty /24 subnet in the same Availability Zone, create a prefix-type subnet CIDR reservation for an available /28 block, and deploy the workers into the new subnet.

**Explanation:** IPv4 prefix delegation requires a contiguous, correctly aligned /28 block. The new subnet provides unfragmented address space, and a prefix-type reservation protects the selected block from individual address assignments while making it available for prefix delegation.

### Question 2 (ANS-C01)

**Question:**

A company runs a stateless application in an Amazon EC2 Auto Scaling group across three Availability Zones. The group uses one small private subnet in each Availability Zone. During traffic spikes, scaling activities fail with insufficient free IPv4 address errors, although the group's maximum capacity and EC2 service quotas are sufficient.

A network engineer has created a larger private subnet in each of the same Availability Zones. The new subnets have the required routes, network ACLs, and connectivity to application dependencies. They have enough available addresses for projected growth and temporary replacement capacity. The application's load balancer can already reach targets in these subnets.

The company must enable scaling into the larger subnets and migrate the existing fleet without reducing healthy application capacity during the migration. It must retain one Auto Scaling group and its three-Availability-Zone deployment.

Which solution meets these requirements?

**Correct answer:** Replace the group's configured subnet IDs with the three larger subnet IDs. Start an instance refresh with a minimum healthy percentage of 100 and a maximum healthy percentage above 100, allowing replacement instances to become healthy before terminating old instances.

**Explanation:** Updating the group's subnet configuration directs subsequent launches into the larger subnets while preserving deployment across all three Availability Zones. An instance refresh migrates the existing fleet. With sufficient temporary capacity, a minimum healthy percentage of 100 and a higher maximum healthy percentage allow launch-before-terminate replacement without reducing healthy application capacity.

### Question 3 (SAA-C03)

**Question:**

A company is expanding from 6 AWS accounts to 80 accounts across two AWS Regions. Each account will contain several VPCs. All VPCs must eventually communicate with one another and with an on-premises network through private IPv4 routing without address translation. The on-premises network uses 10.0.0.0/12. The company has reserved 10.64.0.0/10 exclusively for AWS and requires a /20 CIDR block for each new VPC.

The company wants to automate address allocation across accounts and prevent conflicting allocations as the environment grows. Which addressing plan meets these requirements with the least ongoing administrative effort?

**Correct answer:** Use VPC IP Address Manager (IPAM) Advanced Tier with a delegated administrator. Create a private address pool for 10.64.0.0/10, allocate nonoverlapping Regional pools from it, and share the Regional pools with the accounts. Require new VPCs to obtain /20 allocations from these pools.

**Explanation:** A centrally managed IPAM pool hierarchy can allocate unique address ranges across accounts and Regions. Nonoverlapping Regional pools drawn from 10.64.0.0/10 avoid both inter-VPC conflicts and the on-premises 10.0.0.0/12 range. Allocating VPC CIDRs through the shared pools automates address management as accounts and VPCs are added.

## Practice IP Addressing in a full exam

Questions on IP Addressing in each practice exam, with every answer option and an explanation for each:

- [ANS-C01](https://blowstack.com/practice-exams/aws-certified-advanced-networking-specialty): 11 questions
- [SOA-C03](https://blowstack.com/practice-exams/aws-certified-cloudops-engineer-associate): 10 questions
- [SAA-C03](https://blowstack.com/practice-exams/aws-certified-solutions-architect-associate): 9 questions

## What is IP Addressing

IP addressing gives network interfaces logical addresses that routers use to deliver packets. IPv4 addresses contain 32 bits and are commonly written in dotted-decimal form, such as 10.20.1.15. IPv6 addresses contain 128 bits and use hexadecimal notation. An interface can have multiple addresses, and an address identifies a network endpoint rather than a permanent application identity. Applications should generally use DNS names when endpoints may change.

Cloud networks allocate addresses from ranges expressed using Classless Inter-Domain Routing, or CIDR. For example, 10.20.0.0/16 contains 65,536 IPv4 addresses. The prefix length indicates how many bits identify the network: a larger prefix number means a smaller address range. Dividing that range into subnets such as 10.20.1.0/24 and 10.20.2.0/24 creates separate address ranges for workloads. Each /24 contains 256 total addresses, but not all are necessarily assignable. In an AWS IPv4 subnet, AWS reserves the first four addresses and the last address, leaving 251 assignable addresses in a /24.

In AWS, a virtual private cloud, or VPC, provides the network boundary and has one or more associated address ranges. A subnet takes an address range from its VPC and exists within one Availability Zone. Engineers commonly place application instances in private subnets across multiple Availability Zones and public-facing load balancers in public subnets. Subnet sizing must account for growth, replacement instances during deployments, and network interfaces created by managed services, not just the current number of virtual machines.

Private IPv4 addresses, including addresses from 10.0.0.0/8, 172.16.0.0/12, and 192.168.0.0/16, are not publicly routed on the internet. They can support communication within a cloud network and across connected private networks. Public IPv4 addresses support internet routing, but assigning one does not automatically make a workload reachable. Routing, gateways, security groups, network access control lists, and application listeners must also permit communication.

AWS subnet classification depends on routing, not on the numerical address range. A public subnet has a route to an internet gateway. For an EC2 instance to communicate directly with the internet over IPv4 through that gateway, it also needs a public IPv4 address or an Elastic IP address. The internet gateway maps that public address to the instance's private IPv4 address. A private subnet has no direct route to an internet gateway. Its workloads can initiate outbound IPv4 connections through a public NAT gateway when the necessary routes and internet gateway are configured. NAT does not provide unsolicited inbound internet access to those workloads.

IPv6 offers a much larger address space and can operate alongside IPv4 in a dual-stack network. Globally routable IPv6 addresses do not imply unrestricted access: routes and security controls still govern reachability. In AWS, an egress-only internet gateway supports outbound-initiated IPv6 internet communication while preventing internet hosts from initiating connections through that gateway. IPv6 does not require the public-to-private address translation used for typical EC2 public IPv4 connectivity.

Address planning involves practical trade-offs. Small subnets conserve address space but can exhaust capacity during scaling. Oversized allocations can waste private address space needed for other networks. Overlapping CIDR ranges complicate connectivity, and AWS VPC peering does not support overlapping VPC CIDR blocks. Public IPv4 addresses and NAT gateways can also introduce charges. Plan non-overlapping ranges across cloud environments and on-premises networks, then evaluate addressing, routing, and access controls separately when troubleshooting.

## Learn IP Addressing in lessons

2 short lessons on IP Addressing in 2 certification courses.

- SOA-C03: IP Addressing: CIDR ranges and subnet capacity (Premium), https://app.blowstack.com/lessons/ip-addressing-cidr-ranges-and-subnet-capacity-soa-c03
- SAA-C03: IP Addressing: scalable CIDR allocation (Premium), https://app.blowstack.com/lessons/ip-addressing-scalable-cidr-allocation-saa-c03
