aws
Design and Build a Custom AWS VPC with Public and Private Subnets Using VLSM
This project demonstrates how to design and configure a custom Virtual Private Cloud (VPC) on AWS using Variable Length Subnet Masking (VLSM). I divided a 192.168.0.0/24 network into four public and private subnets based on different host requirements, configured routing and internet connectivity, and deployed an EC2 instance in a public subnet.
About this project
The goal of this project was to understand AWS networking by building a custom network instead of relying on the default VPC. I used VLSM to allocate IP address space efficiently while accounting for AWS-specific subnet size limitations and reserved IP addresses. I configured an Internet Gateway, separate public and private route tables, automatic public IPv4 assignment for public subnets, and a security group with restricted SSH access. Finally, I launched an Ubuntu EC2 instance in a public subnet and verified its network configuration and public IP connectivity.
## What I implemented
* Created a custom AWS VPC using the 192.168.0.0/24 CIDR block.
* Applied VLSM to design two public and two private subnets for different host requirements.
* Configured an Internet Gateway and separate route tables to control public and private network traffic.
* Enabled automatic public IPv4 assignment for public subnets and configured EC2 security group rules.
* Deployed an Ubuntu EC2 instance in a public subnet and verified its IP address and network settings.
* Studied the differences between Network ACLs and security groups for subnet-level and resource-level traffic filtering.
* Reserved unused IP address space for future network expansion and reviewed AWS resource cleanup practices.
## Technologies & Services
AWS VPC · Amazon EC2 · IPv4 · CIDR · VLSM · Public and Private Subnets · Internet Gateway · Route Tables · Security Groups · Network ACLs · Ubuntu · SSH
## Key Takeaway
This project strengthened my understanding of AWS networking, subnet planning, IP address allocation, routing, and network security. It also demonstrated how to build a structured cloud network before deploying workloads, with room for future expansion into NAT Gateways, load balancing, Auto Scaling, and multi-Availability Zone architectures.