← Back to list

Day 5 of 150 Days of DevOps: Building My First AWS Network

After spending yesterday learning AWS networking concepts, today I focused on implementing them inside AWS.

Birendra Sasmal · 2026-06-22 14:01 · 0 claps · 2.2 min read
#aws #cloud-computing #linux #networking
Open on Medium ↗
Wiki topics: EDU · Education & Learning ☁️ · DevOps & Cloud 🔓 · Open Source ⏱️ · Productivity

Day 5 of 150 Days of DevOps: Building My First AWS Network

After spending yesterday learning AWS networking concepts, today I focused on implementing them inside AWS.

Reading about VPCs, subnets, route tables, and internet gateways helped me understand the theory, but creating them manually gave me a much clearer picture of how cloud networking actually works.

https://www.linkedin.com/posts/birendra-sasmal_devops-aws-cloudcomputing-ugcPost-7474816633148956672-VHN0/?utm_source=share&utm_medium=member_desktop&rcm=ACoAAE7yK-oBqqYxP_tcl6ZvIw0NChSBFBPQpKk

Creating a VPC

The first step was creating a Virtual Private Cloud (VPC).

A VPC provides an isolated networking environment within AWS where resources can communicate securely.

Everything else I created today was built inside this VPC.

Creating Public and Private Subnets

Once the VPC was ready, I created two types of subnets:

Public Subnet

  • Designed for resources that need internet access.

Private Subnet

  • Designed for resources that should remain isolated from the internet.

This separation is a common practice in real-world cloud environments.

Setting Up an Internet Gateway

Next, I created and attached an Internet Gateway to the VPC.

The Internet Gateway acts as the bridge between the VPC and the public internet.

Without it, resources inside the VPC cannot communicate with the outside world.

Configuring Route Tables

After attaching the Internet Gateway, I configured Route Tables.

Route Tables determine where network traffic should be directed.

For the public subnet, I added a route that sends internet-bound traffic to the Internet Gateway.

This is what makes a subnet “public.”

Associating Subnets

Finally, I associated the route tables with the appropriate subnets.

This helped me understand that simply creating resources is not enough. Every component must be connected correctly for networking to function as expected.

Key Lessons

Today’s practical session taught me that AWS networking is like assembling a puzzle.

Each component serves a specific purpose:

  • VPC provides isolation.
  • Subnets organize resources.
  • Internet Gateway enables internet access.
  • Route Tables direct traffic.

Individually, they are simple concepts.

Together, they form the foundation of cloud infrastructure.

What’s Next?

Tomorrow, I plan to launch EC2 instances and explore how compute resources interact with the networking components I created today.

Closing

I am Birendra Sasmal, a BCA student documenting my journey toward becoming a DevOps Engineer.

Follow along as I learn cloud computing, Linux, AWS, Docker, Kubernetes, Terraform, CI/CD, and more.


메타데이터
post_id
d35dbb27da72
slug
day-5-of-150-days-of-devops-building-my-first-aws-network-d35dbb27da72
url
https://medium.com/@birendrasasmal/day-5-of-150-days-of-devops-building-my-first-aws-network-d35dbb27da72
canonical_url
https://medium.com/@birendrasasmal/day-5-of-150-days-of-devops-building-my-first-aws-network-d35dbb27da72
author_url
https://medium.com/@birendrasasmal
status
ok
fetched_at
2026-06-23 03:48:11