AWS re/Start – My Week 4 Experience

#aws #restart #cloudcomputing #beginners

Ember month is finally here; can you believe it? Just like that, we’re already in week 4! Today is September 1st, and wow, another birthday is just around the corner 🎂. No prior warning, no time to mentally prepare for getting older. But let’s put that aside and get back to AWS Restart.

Day 15:

Today started a bit slow, but the pace picked up as the day went on. We’re still deep into networking, and I’m slowly wrapping my head around it. I keep telling myself: it’s not about how fast, but how far I go. Little by little, I know I’ll get there.
Our case scenario today involved troubleshooting a network issue for a customer. I acted as a cloud support engineer, helping a new cloud user who just wanted to reach her site. The issue? The inbound rule in her security group wasn’t defined. I edited the rule so requests could reach the server, and voilà—the customer could send a request and receive a response. Later, we reviewed additional networking protocols.

Day 16:

Continuation of networking protocols. Today felt more like a debugging session in the lab. The issue was again related to security group configurations; inbound rules were incorrect. It reminded me that networking requires careful attention to detail; one small mistake can break everything.

Day 17:

AWS Restart isn’t just about technical skills; soft skills matter too. Protecting yourself is important, but protecting digital assets is equally vital.

Day 18:

Continuing with digital asset protection, we learned how to implement network hardening to identify and fix security loopholes in both infrastructure and code. For code stored in the cloud, AWS Inspector helps check for vulnerabilities, allowing you to take action and secure your resources.