
From Compute to Networking: My Hands-on Journey with Amazon VPC
After completing my Amazon EC2 lab, I explored Amazon VPC to understand the networking side of AWS. In this article, I share the key concepts I learned through the AWS Skill Builder hands-on lab and how they helped me understand secure cloud networking.
After completing my first hands-on lab on Amazon EC2, I wanted to learn what happens behind the scenes when we launch a virtual server. During my learning journey, I came across Amazon VPC, a service that forms the foundation of AWS networking.
At first, terms like VPC, Subnets, Route Tables, Internet Gateway, and Security Groups seemed confusing. But after completing the Introduction to Amazon VPC lab on AWS Skill Builder, these concepts became much easier to understand.
In this article, I'd like to share what I learned and how this lab helped me build a stronger understanding of AWS networking.
What is Amazon VPC?
Amazon Virtual Private Cloud (VPC) is a service that allows you to create your own private network inside the AWS Cloud.
You can think of a VPC as your own virtual office or campus. Just as an office has rooms, doors, and security rules, a VPC provides a secure environment where your AWS resources can communicate safely.
Instead of AWS deciding how everything connects, a VPC gives you control over your network configuration, making your applications more secure and organized.
Why Do We Need a VPC?
Before this lab, I thought cloud computing was mainly about launching servers like EC2. But I learned that every server also needs a network to communicate with users and other resources.
Amazon VPC helps us:
- Build a secure network for AWS resources.
- Control which resources can access the internet.
- Separate public and private resources.
- Manage network traffic efficiently.
This made me realize that cloud networking is just as important as cloud computing.
The Networking Concepts That Finally Made Sense
One thing I really liked about this lab was that it explained networking concepts through practical examples instead of just theory.
VPC – Your Private Network
A VPC is your own private network inside AWS. All the resources you launch, such as EC2 instances, are placed inside a VPC.
Without a VPC, AWS resources wouldn't have a secure environment to communicate.
Subnet – Dividing the Network
A Subnet is a smaller section inside a VPC.
It helps organize resources based on their purpose.
For example, one subnet can contain web servers, while another can contain databases.
This makes the network easier to manage and improves security.
Public Subnet
A Public Subnet contains resources that need internet access.
For example:
- Web Server
- Public Website
These resources communicate with users over the internet.
Private Subnet
A Private Subnet contains resources that should not be directly accessible from the internet.
For example:
- Database Server
- Internal Applications
Keeping these resources private improves security.
Internet Gateway
An Internet Gateway acts like the main entrance to your VPC.
It allows resources inside a Public Subnet to communicate with the internet.
Without an Internet Gateway, users outside AWS cannot access your public resources.
Route Table
A Route Table contains rules that tell AWS where network traffic should go.
You can think of it as Google Maps for your cloud network—it decides the path that data follows to reach its destination.
Security Group
A Security Group works like a virtual firewall.
It controls which traffic is allowed to enter or leave an EC2 instance.
For example:
- Allow HTTP (Port 80)
- Allow HTTPS (Port 443)
- Allow SSH (Port 22) only for administrators
This helps protect cloud resources from unauthorized access.
What I Learned During the Lab
During the Introduction to Amazon VPC lab, I learned how to:
- Create an Amazon VPC using the VPC Wizard.
- Understand the purpose of a VPC.
- Create and explore subnets.
- Understand the difference between Public and Private Subnets.
- Learn how an Internet Gateway provides internet connectivity.
- Explore Route Tables and their role in directing traffic.
- Understand how Security Groups improve the security of cloud resources.
The guided lab made these concepts much easier to understand because I could see how each component worked together.
My Biggest Takeaway
The biggest lesson I learned from this lab is that launching a server is only one part of building a cloud application.
A secure network is equally important.
Amazon VPC provides that secure foundation by allowing developers to organize resources, manage network traffic, and control access.
This hands-on experience helped me understand that cloud networking is not as difficult as it first seems—it becomes much clearer once you understand how each component fits together.
What's Next?
Completing this lab has made me more interested in AWS networking.
As I continue learning through AWS Skill Builder, I'm looking forward to exploring more AWS services and understanding how they work together to build secure, scalable, and reliable cloud solutions.
Every hands-on lab gives me a better understanding of cloud computing, and I'm excited to continue sharing my learning journey with the AWS community.
Thank you for reading!
Enjoyed reading this content? Let the author know!
Your likes, comments, shares, and saves help creators reach more builders.
Loading recommendations
Loading article