## TL;DR

Object Ownership: with BucketOwnerEnforced, ACLs are disabled entirely, so old ACL-based grants silently stop working. This is the layer everyone forgets, because the error says S3 while the denial lives in KMS.

## Steps

1. Reproduce with the AWS CLI and --debug to see the exact request.
2. Temporarily test with an admin-scoped role in a sandbox to isolate policy from code bugs. Narrow back down after.
3. Fix exactly one layer, retest, repeat. Changing IAM and the bucket policy at once teaches you nothing.

## When to use

You are seeing this: "AccessDenied" from S3 is five different problems wearing one error message. Use this skill when you run into "S3 403s: which layer is actually denying you".

## When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

## Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

## Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.
