Before starting the first module of AWS Cloud Practitioner Essentials, I mostly thought of cloud as a place to host a backend, database, or run computing workloads.
The biggest shift for me came from learning about AWS Global Infrastructure, especially Regions and Availability Zones.
I had used large-scale web applications many times without thinking much about what happens when physical infrastructure fails. Learning about fault tolerance helped me understand how applications can be designed to remain available even when part of the underlying infrastructure has a problem.
The Shared Responsibility Model was another concept that stood out.
Before this module, I assumed that moving an application to the cloud meant the provider would handle most of the security. Now I understand that responsibility changes depending on the service and deployment model. AWS secures the infrastructure of the cloud, while customers still remain responsible for important parts of what they run in the cloud.
The module also changed how I think about deployment and scaling.
Previously, I mainly associated scalability with backend implementation. Now I see that infrastructure and deployment choices also directly influence scalability, elasticity, availability, and cost.
As I continue learning about solution architecture, I think this is one mindset I want to develop further:
not only asking whether a system works, but understanding the trade-offs behind how it is deployed, scaled, secured, and operated.
Call to action
I am still at the beginning of my AWS learning journey, so I would be interested to hear how others first changed their perspective on cloud architecture.
What was the first cloud concept that made you think differently about how systems are designed?
Loading article