Learning Networking for Cloud Engineering
My Cloud Journey: Networking, VPC Peering, and First Roadblocks
Starting a journey into cloud engineering means drinking from a firehose of information.
This week, I dove straight into the core of how the cloud actually talks to itself: networking.
Here is what my last couple of days looked like.
July 6: The "Aha!" Moment with VPC Peering
I spent the first half of the day grinding through the theory of networking and how the internet works under the hood for cloud infrastructure. Once the concepts made sense, it was time to build.
The Goal: Connect two separate Virtual Networks (VPCs) together using VPC Peering so that a Virtual Machine in one network could ping a VM in the other using only their private IP addresses.
The Reality Check: I hit a massive roadblock. I was trying to manually add route tables to connect the two networks.
What I didn't realize is that Azure handles those route tables automatically when you set up peering. By forcing my own custom route tables into the mix, I accidentally overwrote Azure's default routing, and the VMs completely lost track of each other. Nothing was pinging.
The Fix: After a bit of troubleshooting, I deleted my manual route tables, let Azure do its thing, and it worked flawlessly. Lesson learned: sometimes you need to get out of the provider's way.
July 7: Shifting Gears to Automation
With basic networking checked off, I officially started learning Python.
In cloud engineering, you don't want to build everything manually by clicking through a dashboard forever. Python is going to be my tool for automating infrastructure, writing scripts, and making things scale.
It's just the beginning of the programming side, but I’m excited to see how it ties back into the infrastructure I'm learning to build.
What’s your favorite "oops" moment when learning a new cloud platform? Let me know in the comments!
