
From Auditing to AWS: How I Learned Who Owns Security in the Cloud
A plain-language breakdown of who secures what in AWS, and why the responsibility boundary shifts from EC2 to managed services like RDS and Lambda. Written from a security auditor's perspective for Cloud Practitioner learners.
When I started my AWS journey, one question kept coming back: "If the cloud is managed by AWS, who is actually responsible for security?"
Coming from a cybersecurity and auditing background, this question wasn't just academic for me, it's the foundation of every control, every risk assessment, and every compliance conversation.
The answer comes down to one of the most important concepts for the AWS Certified Cloud Practitioner exam and for real-world cloud work: the Shared Responsibility Model.
In this article, I'll explain it in plain language, share the mental model that finally made it click for me, and highlight the mistakes beginners (myself included) often make.
The Core Idea: "Of" vs. "In"
The whole model can be summarized in two small words:
- AWS is responsible for security of the cloud.
- You are responsible for security in the cloud.
That single distinction unlocks everything.
Think of it like renting an apartment:
- The building owner secures the structure, the locks on the main entrance, and the foundation.
- You are responsible for locking your own door, deciding who gets a key, and protecting what's inside.
AWS secures the building's underlying infrastructure. How you configure and use what is inside remains your responsibility.
But there's one important nuance: the responsibility boundary isn't identical for every AWS service.
With Amazon EC2, for example, you manage more of the stack, including the guest operating system and its security configuration. With more managed or abstracted services, AWS takes responsibility for more of the underlying layers.
Your responsibility doesn't disappear, it shifts.
Where IAM Fits (and Why It Matters So Much)
If security in the cloud is your job, then IAM (Identity and Access Management) is one of your most important security tools.
IAM helps you define:
- Who or what can access AWS resources (identities)
- What they are allowed to do (policies and permissions)
- How workloads obtain temporary permissions (roles)
- And, ideally, how to enforce the principle of least privilege
From an auditor's perspective, IAM plays a role similar to an access control framework: it helps define who or what can access AWS resources, which actions they can perform, and under what conditions.
Misconfigured permissions can create significant security exposure, not because AWS failed to secure the underlying infrastructure, but because access configuration remains part of the customer's responsibility.
Which service surprised you the most? Drop it in the comments.
What Beginners Often Get Wrong
Here are the misconceptions I had to unlearn:
- "AWS secures everything." ❌ AWS secures the underlying cloud infrastructure, but you still have responsibilities for areas such as your data, access controls, and configurations.
- "Managed services mean zero responsibility." ❌ With a managed service like Amazon RDS, AWS takes responsibility for more of the underlying infrastructure and platform management. You still remain responsible for areas such as access control, data protection, and the security configurations available to you.
- "Security is a one-time setup." ❌ It's continuous, permissions, credentials, and configurations need ongoing review (something every auditor knows well).
How to Actually Learn This
If you're preparing for the Cloud Practitioner exam, don't just memorize the model, map it to real services:
- Take a service like Amazon S3 and ask: What does AWS secure? What do I secure?
- AWS secures the underlying storage infrastructure and its physical environment.
- You are responsible for configuring access controls, bucket policies, encryption choices, and whether public access is permitted when your use case requires it.
Then repeat the exercise with EC2, RDS, Lambda, and VPC.
Ask the same two questions each time:
What does AWS secure? What do I secure?
Once you start comparing services this way, the Shared Responsibility Model stops being an abstract definition and becomes something practical.
Final Thoughts
The Shared Responsibility Model isn't just an exam topic, it's a mindset shift that separates "using the cloud" from "securing the cloud."
Coming from auditing, what helped me most was treating each responsibility like a control with an owner. Once you know who owns what, security decisions become much clearer.
I'm still early in my AWS journey, and I'm documenting it publicly to learn alongside the community.
So I'd love to hear from you:
- How did the Shared Responsibility Model finally "click" for you?
- What's one AWS service where you found the responsibility split surprising?
Let's learn and secure the cloud together. 🚀☁️
Enjoyed reading this content? Let the author know!
Your likes, comments, shares, and saves help creators reach more builders.
Loading recommendations
Loading article