Cloud Engineer Beginner Diary: Week 1
Introduction
I’ve just started learning cloud engineering, and so far I’ve been building a base in cloud computing, networking, operating systems, and Amazon Web Services (AWS). I’m learning how the cloud works, how computers talk to each other online, and how cloud setups are built and kept secure.
I began with the basics of cloud computing: what it is, why it’s useful, and the different ways it can be deployed. I also learned about the Software Development Life Cycle (SDLC), which covers the steps of planning, building, testing, and maintaining software. Since I worked at a bank and used a lot of systems there, it was easier to picture how data gets stored and managed.
After that, I created my own AWS account and learned why it’s so important to lock it down. I also set up a budget to keep an eye on spending. That showed me cloud engineering isn’t just launching services. You also have to look after security, resources, and costs.
I’ve also been learning how the internet works, including virtualization, IP addresses, DNS, and the parts that make up a network. In the hands-on labs, I used curl, traceroute, and ping on nike.com to send requests, follow the path data takes to reach the site, and check whether the connection was working. I also learned how to find the IP address behind a website like nike.com and see what systems it’s running.
I’ve started looking into operating systems, cloud operating systems, databases, and network tools too. These help me see what’s underneath cloud infrastructure and how applications run and connect.
DISCLAIMER: THE DOMAIN USED IN THE EXAMPLES IS FOR DOCUMENTATION EXAMPLES WITHOUT NEEDING PERMISSION. THIS IS NOT A SERVICE; AVOID RELYING ON IT FOR TESTING AND MONITORING PURPOSES.
Get Marc Steve Jimenez’s stories in your inbox
Join Medium for free to get updates from this writer.
This is an example of curl requests:
These are screenshots of various trace requests with parameters:
This is an example for a ping request:
I’m still at the beginning, but every lesson and lab helps me connect what I’m learning to real situations. My next step is to build more projects, get hands-on practice with AWS, and keep growing toward a cloud engineering role.
