Q: What is the difference between an IAM policy attached to a user vs a resource policy attached to an S3 bucket?
- Identity policy (attached to IAM user/role/group) — defines what that identity CAN do across AWS.
Want to master this scenario in a live sandbox? Stephane Maarek's AWS Certified DevOps Engineer Professional Masterclass on Udemy covers this exact problem with hands-on terminal drills.
🛠️ Production Runbook & Step-by-Step Resolution
Direct Answer: "AWS reliability requires differentiating between AWS control plane limits and host-level resource exhaustion. When addressing this question, I walk the interviewer through our production incident runbook: isolating the blast radius, checking diagnostic logs and metrics, and applying a safe fix."
Initial Diagnostics & Root Cause Analysis
Example: An S3 bucket policy can grant access to an IAM user in a different AWS account — the identity policy alone can't cross account boundaries without a resource policy (or role trust policy) on the other side.
- Identity policy (attached to IAM user/role/group) — defines what that identity CAN do across AWS.
- Resource policy (attached to S3 bucket, KMS key, SNS topic) — defines WHO can access that specific resource.
Remediation & Permanent Safeguards
When both exist: for same-account access, the union of both policies is the effective permission. For cross-account: both must allow the action. Explicit Deny anywhere always wins, regardless of Allows.
- Identity policy (attached to IAM user/role/group) — defines what that identity CAN do across AWS.
- Resource policy (attached to S3 bucket, KMS key, SNS topic) — defines WHO can access that specifi...
Senior hiring managers and bar raisers evaluate how you prioritize during outages. Avoid these common anti-patterns:
- Relying on legacy bucket ACLs instead of modern S3 Block Public Access and IAM bucket policies when configuring difference policy attached AWS recommends disabling ACLs (Bucket Owner Enforced) in favor of centralized declarative bucket policies and account-level Block Public Access controls.
-
Confusing SSE-S3 encryption with KMS customer-managed key (SSE-KMS) authorization policies when configuring difference policy attached
Accessing SSE-KMS encrypted objects requires both
s3:GetObjectandkms:Decryptpermissions; neglecting KMS key policies causes silent 403 Forbidden errors. - Using sequential timestamps or predictable prefixes for high-throughput S3 read and write keys when configuring difference policy attached Sequential key prefixes limit S3 horizontal partitioning; randomized hash prefixes distribute workloads across partitions to achieve 3,500 PUT and 5,500 GET requests/sec.
- Failing to audit S3 object delete markers when troubleshooting missing versioned objects when configuring difference policy attached Issuing a DELETE on a versioned bucket only adds a delete marker; engineers must retrieve previous versions or purge markers to restore data.