Day 2 of My 120-Day DevOps Learning Journey
I learned the basics of AWS services like EC2, S3, and RDS. Today, I moved one step deeper into AWS networking concepts, which are the foundation of cloud infrastructure.
What I Learned Today
VPC (Virtual Private Cloud)
A VPC is like my own private network inside AWS where I can launch and manage resources securely.
Steps to Create a VPC:
Select AWS Region Create a VPC Create Public Subnets in different Availability Zones (AZs) Create Private Subnets in different Availability Zones (AZs) 2. Availability Zones (AZs)
Availability Zones are separate data centers within a region.
Example in Mumbai Region:
ap-south-1a ap-south-1b ap-south-1c
Using multiple AZs improves:
High Availability Fault Tolerance Disaster Recovery 3. Public Subnet
A public subnet is connected to the internet through an Internet Gateway.
Resources commonly deployed here:
Web Servers Bastion Hosts Load Balancers
Example: A customer visits a website. The web server must be accessible from the internet, so it is placed in a public subnet.
Private Subnet
A private subnet does not allow direct internet access.
Resources commonly deployed here:
Application Servers Database Servers Internal Services
Example: An RDS database should not be directly accessible from the internet. It is placed inside a private subnet for security.
Public Server vs Private Server Public Server Private Server Has Public IP No Public IP Accessible from Internet Accessible only within VPC Hosts websites and APIs Hosts databases and internal apps Less secure if misconfigured More secure
Load Balancer
A Load Balancer distributes incoming traffic across multiple servers.
Why Do We Need It?
Imagine:
10,000 users visit a website simultaneously. One server may become overloaded. The Load Balancer distributes requests across multiple servers.
Benefits:
✅ High Availability
✅ Better Performance
✅ Fault Tolerance
✅ Scalability
I learned that cloud infrastructure is not just about launching servers. Designing secure and highly available systems starts with proper networking.
Understanding VPCs, Public and Private Subnets, Availability Zones, and Load Balancers is the first step toward building production-ready cloud architectures.
