DEV Community

Ijay
Ijay

Posted on

AWS re/Start – My Week 3 Experience

Week 3 has reminded me that the key to progress is simply showing up, regardless.

Day 10

I was not feeling well today; perhaps it was due to the weather, but that did not prevent me from attending class. That’s one thing I appreciate about virtual learning compared to a traditional classroom. I took my medication, which made me sleepy, so honestly I barely remember half of what was taught. Thankfully, I have people I can ask questions, and the AWS Restart LMS is always there to catch me up.
By the second lecture, I managed to focus better and even contributed to the class. We continued with Linux and Bash, working with commands, managing system processes, and doing some practicals. That’s about all I can recall from today.

Day 11

We wrapped up Linux commands and moved into Bash scripting. This part is very important as a cloud engineer, alongside programming languages like Node.js or Python. One thing I truly love about AWS Restart is the hands-on sessions. AWS handles the heavy lifting, so you don’t even need your own AWS account to practice.

Day 12

Networking is one of the core areas in cloud engineering, along with compute, storage, and databases. Honestly, learning networking was one of the main reasons I joined AWS Restart. In simple terms, a network is a group of computers or devices connected together to communicate and share resources. It’s how computers “talk” to each other, sending requests and receiving responses.
We also touched on client devices, servers, network interface cards (NICs), switches, and routers, all key players in making communication happen.

Day 13

We continued with networking concepts, this time focusing on LAN and WAN, different protocols, and how connection structures work. We also learned how IP addresses uniquely identify physical devices and how port numbers make sure data goes to the right service.

Day 14

Today, we continued our exploration of networking, specifically focusing on Virtual Private Clouds (VPCs). A VPC defines an isolated section in AWS where cloud resources can be provisioned. From there, we explored subnets and other related topics.
I’ll be honest, CIDR calculations are still a bit tricky for me, but I’m confident that with time and practice it will all come together.

Resources


Come say hi on Twitter and LinkedIn, or check out my work on GitHub.


Thanks for following my journey—see you in Week 4!

Top comments (0)