Concept Flow - Why IAM policies protect data
User makes request
IAM policy checks permissions
Allow access
Data accessed
When a user requests data, IAM policies check if they have permission. If yes, access is allowed; if no, access is denied.
User requests DynamoDB data IAM policy evaluates permissions If allowed, data is returned If denied, access is blocked
| Step | Action | IAM Policy Check | Result | Data Access |
|---|---|---|---|---|
| 1 | User sends request to DynamoDB | Check if user has permission | Permission found | Access allowed |
| 2 | User sends request to DynamoDB | Check if user has permission | Permission not found | Access denied |
| 3 | Access denied | No further checks | Request blocked | No data returned |
| Variable | Start | After Step 1 | After Step 2 | Final |
|---|---|---|---|---|
| User Request | None | Sent | Sent | Completed |
| IAM Permission | Unknown | Found or Not Found | Determined | Determined |
| Access Status | None | Allowed or Denied | Denied | Finalized |
IAM policies check user permissions on each request. If permission exists, access is allowed. If permission is missing, access is denied. This protects data by controlling who can read or write. Always attach correct IAM policies to users or roles.