Chapters0/41 ▾
- 1.Cloud Concepts: Benefits & Economics0/4
- 2.Cloud Concepts: Well-Architected & Migration0/5
- 3.Security: Shared Responsibility & Compliance0/4
- 4.Security: IAM & Access Management0/4
- 5.Security: Services & Resources0/4
- 6.Technology: Deployment & Global Infrastructure0/4
- 7.Technology: Compute & Networking0/4
- 8.Technology: Databases & Storage0/4
- 9.Technology: AI, Analytics & Other Services0/4
- AI and machine learning services: pre-trained services and SageMaker AI
- Analytics services: Glue, Athena, Redshift, EMR, OpenSearch, Kinesis and Amazon Quick
- Messaging and workflows: SQS, SNS, EventBridge, Step Functions, Amazon Connect and SES
- Developer tools, cloud desktops, AWS Amplify and AWS IoT Core
- 10.Billing, Pricing & Support0/4
- EC2 purchasing options: On-Demand, Spot, Savings Plans, Reserved Instances and dedicated hardware
- Data transfer costs, consolidated billing and cost allocation tags
- Cost management tools: Pricing Calculator, Cost Explorer, Budgets, Cost and Usage Reports and Compute Optimizer
- AWS Support plans, Trusted Advisor, AWS Health and where to get help
Chapter 4 · Lesson 2 of 4
IAM users, user groups and roles
1 min read
| Identity | What it is | Key limit |
|---|---|---|
| IAM user | One person or workload in one account, with long-term credentials | Belongs to a single account |
| IAM user group | A set of IAM users that share attached policies | Holds only IAM users, not roles or other groups |
| IAM role | A set of permissions that a trusted person, service or account assumes | Gives temporary credentials, no long-term ones |
Groups make permissions follow a job. When someone changes teams, move the user out of the old group and into the new one, and both sets of permissions change in one step. Roles are the answer whenever code or another account needs access.
An application on Amazon EC2 should get its permissions from a role attached to the instance, which hands it temporary credentials that AWS rotates. Storing an IAM user's access keys on the instance or in the code, even encrypted, still leaves long-term secrets lying around.
For access across accounts, create the role in the account that owns the resources. Its permissions policy says what is allowed, and its trust policy names who may assume it. Example: an audit team in a security account needs to read logs in a production account.
Production gets a read-only role that trusts the security account, and auditors assume it when needed, with no users or keys copied anywhere.
Check yourself
1. An application on an Amazon EC2 instance needs to read objects from an Amazon S3 bucket. Which approach follows AWS best practice?
2. A security team that works in one AWS account needs to review resources in a second AWS account owned by the same company. What is the recommended way to give the team this access?
Facts checked 2026-11-15 · Sources: AWS Certified Cloud Practitioner (CLF-C02) Exam Guide, IAM User Guide: Security best practices in IAM, AWS IAM Identity Center User Guide
AWS Cloud Practitioner cheat sheet: every key fact on one page →