AWS Builder Center
5 Concepts from AWS Cloud Practitioner That Changed How I See the Cloud

5 Concepts from AWS Cloud Practitioner That Changed How I See the Cloud

I'm currently studying for the AWS Certified Cloud Practitioner exam, and even as a developer who already deploys applications, some fundamentals completely changed how I think about building systems. Here are the five that stuck with me the most.

  1. The Shared Responsibility Model
    AWS is responsible for the security of the cloud (data centers, hardware, network), while you're responsible for security in the cloud (your data, IAM permissions, configurations). A lot of security incidents don't come from AWS failing, but from users misconfiguring things like public S3 buckets.
  2. Regions and Availability Zones
    A Region is a geographic area, and each one has multiple Availability Zones, which are isolated data centers. Spreading your application across more than one AZ means a failure in one data center doesn't take your whole system down. High availability starts with this simple decision.
  3. Pay-as-you-go changes architecture decisions
    In the cloud, cost is part of the design. Choosing between EC2, Lambda, or containers isn't only a technical decision but also a financial one. Understanding pricing models early helps avoid both surprise bills and overengineering.
  4. Least Privilege with IAM
    Every user, application, and service should have only the permissions it actually needs. It sounds obvious, but giving full admin access "just to make it work" is one of the most common mistakes, and fixing it later is much harder.
  5. The Well-Architected Framework
    AWS organizes good architecture into six pillars: operational excellence, security, reliability, performance efficiency, cost optimization, and sustainability. It works like a checklist to evaluate any system, from a small side project to a large production workload.
What's next:
I'm finishing AWS Cloud Practitioner Essentials on Skill Builder and then moving to exam prep and hands-on labs. My goal is not just to pass the exam, but to apply these concepts in the projects I build.
Any opinions in this article are those of the individual author and may not reflect the opinions of AWS.
Enjoyed reading this content? Let the author know!

Your likes, comments, shares, and saves help creators reach more builders.

Loading recommendations

Loading article