Core lesson 8 of 18Topic: IAM: identity and permissions
What is AWS IAM? Authentication and permissions for beginners
AWS Identity and Access Management (IAM) controls access to AWS resources. Authentication establishes who is making a request; authorization decides whether that request is permitted. Follow an internal reporting app to understand why signing in does not automatically give permission to read a file.
Describe a request using its principal, action and resource. Distinguish successful authentication from permission to act, and separate human access from application access.
No AWS account or keys are needed. Imagine an internal app reading a monthly report.
Start with who, what and which resource
A principal is the identity making a request. An action is the requested API operation, and a resource is its target. “Use S3” is too broad to analyze. Our example fixes one request: an app using its reporting role calls s3:GetObject for report.csv.
- Reporting role → GetObject / report.csvMakes the request using this identity
- GetObject / report.csv → Applicable permissionsCheck action, resource and relevant context
- Reporting role
- The identity used by the app, considered separately from an employee signing in.
- GetObject / report.csv
- The read operation and target file form one specific request.
- Applicable permissions
- Compare applicable policies with request context. This is not the full AWS evaluation algorithm.
| Element | Our example | Do not confuse it with |
|---|---|---|
| Principal | The app using its reporting role | The name of the person operating a screen is not enough |
| Action | s3:GetObject: retrieve an object | s3:PutObject is a different operation |
| Resource | report.csv in demo-bucket | Other objects in the same bucket |
Separate access for people and applications
An IAM role is an identity that can be assumed to obtain temporary credentials. A role is not automatically safe: who may assume it and what its permissions allow are distinct design questions.
| Actor | Start by considering | Avoid as a default |
|---|---|---|
| People | Federation or IAM Identity Center with temporary access | Using root for everyday work |
| Apps running on services such as EC2 | An appropriate IAM role with the required permissions | Embedding long-lived access keys in code |
| The account root user | Strong protection for tasks that actually require root | Sharing root credentials with apps or coworkers |
Three distinctions that prevent mistakes
| Observation | What it does and does not establish |
|---|---|
| A role named “administrator” | The name is descriptive; inspect its actual permissions |
| One Allow exists | This does not establish the outcome of all applicable controls |
| A network path is reachable | Connectivity and permission to perform an AWS API operation are separate questions |
Apply the request to a policy statement
- Write the principal, action and resource on one line.
- Change “read” to “save” and identify the action that changes.
- Read Effect, Action and Resource in the JSON lesson, then change one condition at a time in the IAM lab.
Check, then explain in your own words
- Describe the principal, action and resource in the report example.
- Explain why sign-in and GetObject permission are separate.
- Continue to the IAM policy JSON lesson.
Check your understanding: Must you check again if the same role requests a different file?
Yes. The resource in the request has changed.
The principal may be unchanged, but action, resource and conditions must match the new request. One successful read does not establish access to every object.
Sources and conditions checked
The official references used in this lesson are collected here with their scope, conditions and corresponding sections. Independent expert review and live AWS comparison have not been performed.
- What is IAM?Checked:
Scope and conditionsIdentity and access concepts
Used in this lessonStart with who, what and which resource Authentication is not permission to perform every action Separate access for people and applications Three distinctions that prevent mistakes
- IAM security best practicesChecked:
Scope and conditionsFederation, temporary credentials and least privilege
Used in this lessonSeparate access for people and applications
- IAM policy evaluation logicChecked:
Scope and conditionsPolicy types and context matter; identity-only lab is a subset
Used in this lessonStart with who, what and which resource Authentication is not permission to perform every action Three distinctions that prevent mistakes