This week’s discussion on cloud infrastructure management gave me a clearer picture of just how dominant AWS is in the cloud space. Reading through my classmates’ posts, I kept noticing how naturally CloudWatch and Auto Scaling came up, and it reinforced how deeply those tools are embedded in how modern infrastructure actually works. The scale-up capability specifically stood out to me. The idea that a system can detect a traffic surge and respond automatically, without anyone touching a keyboard, is something I understood conceptually before but feel more concretely now.
What landed differently for me this week was the conversation around cost visibility. For SoulSprouts, I’m not worried about handling ten times normal traffic or configuring complex automation pipelines. What I do need to understand is what I’m spending, why, and whether it’s sustainable. Tools like AWS Cost Explorer represent something real to me not just a course concept. A small, registered business doesn’t have margin for surprise cloud bills, and this discussion reminded me that cost awareness isn’t just a feature to add later. It’s the foundation everything else should be built on.
That framing: cost visibility as foundation, not afterthought, is something I’ll carry forward into how I think about infrastructure decisions for SoulSprouts going forward.
Leave a comment