My Experience Digging Deep Into the AWS Advanced Networking Outline as an Associate
So I decided to spend some time digging into the AWS Advanced Networking certification course on Cloudacademy. First of all, I had been struggling with two choices:
Dive right into the Kubernetes Cloud Native Associate (KCNA), with an end goal of understanding Kubernetes Networking, aka, networking at the Application layer.
Understand this layer of Cloud networking first and see if I can settle in. Then, proceed right into Kubernetes networking after gaining a few more years of experience.
Now, option 2 made a lot of sense because I’ve seen a Kubernetes cluster deployed across two regions on AWS. It was just too interesting enough to not explore the networking outside the Kubernetes cluster.
Also, I have some pre-official working experience for a while working on the AWS platform, so it made sense to dig deeper into the cert and understand how all the technologies worked. While I focused more on building my Terraform skills afterward.
Anyways, so far the course is very interesting. It felt good to see how a DNS resolver is configured within the cloud & on-premises too. Also, how connections span outside the cloud, leveraging a Site-to-Site VPN, or even a direct connection too.
Also, seeing how IP addresses on-premises get propagated into the cloud via BGP was so cool.
I also enjoyed exploring how a load balancer works. I see that it is also used with a Kubernetes cluster, from the blog I referenced above.
I actually had plans to code every lab in the course via automation, specifically using Terraform. But seeing how some concepts required going into devices every time to configure a router so it does BGP or establishes two tunnels for site-to-site connections, other concepts on top of it could work. Made it tiring to continue even if I understand how it works.
However, I am looking to finish my Terraform Associate course outline, and then improve on the AWS Networking labs I have written so far and have published on GitHub. When I am done, I plan to dive right into the Kubernetes Cloud Native Associate. I am happy to have satisfied my curiosity so far in this layer. Using Git via the CLI is something I still struggle with now. Understanding, how branches work, etc. Maybe it’s best to dive into it after my KCNA, or while I am officially working. As an infrastructure engineer, properly understanding how an infrastructure works is first paramount.
Is The Knowledge a Waste?
Personally, I don’t think it is. Honestly, if I had skipped this layer and gone right into Kubernetes, it’d suck. As when Network engineers at this layer are having conversations, I’ll simply be dumbfounded. Which isn’t great for me. I also believe it makes one a better cloud network architect too.
I also took some time to work on the Azure fundamentals too. Right now, I do not know what platform I’ll be working on when I begin doing DevOps with Kubernetes, could it be Azure or AWS, I can’t say specifically.
But I’ll say I’ve had a lot of fun so far. Tinkering with these technologies to see what works for you is always worth it. But it’s not advisable especially if you haven’t worked with it previously for a while. It is always best to seek guidance from senior engineers instead of while away studying the whole thing.
Personally, I wouldn’t have chosen to go into Kubernetes this early. But I keep seeing non-computer-networking undergrads explore it. It just makes sense to give it a shot as a new graduate & associate, and a computer networking nerd too.