Study guide
1.1 IAM Fundamentals — Users, Groups, Roles, and Policies
AWS Solutions Architect Associate SAA-C03
Track your progress as you read
Finished sections get a check mark.
1 Introduction
About the AWS Solutions Architect Associate (SAA-C03) Exam Study Strategies and Exam Tips for SAA-C03 The AWS Well-Architected Framework
2 Domain 1: Design Secure Architectures (30%)
1.1 IAM Fundamentals — Users, Groups, Roles, and Policies 1.2 AWS Organizations, SCPs, and Multi-Account Strategy 1.3 VPC Security — Security Groups, NACLs, and VPC Endpoints 1.4 Encryption, KMS, and Secrets Management 1.5 AWS WAF, Shield, and Network Firewall 1.6 GuardDuty, Inspector, Macie, and Security Hub 1.7 The Shared Responsibility Model for Solutions Architects 1.8 Data Protection, Compliance, and Audit Services
3 Domain 2: Design Resilient Architectures (26%)
2.1 Elastic Load Balancing (ELB) — ALB, NLB, and GWLB 2.2 EC2 Auto Scaling — Dynamic, Predictive, and Scheduled 2.3 Multi-AZ and Multi-Region Architectures 2.4 Disaster Recovery Strategies — RTO and RPO 2.5 Decoupling with SQS, SNS, and EventBridge 2.6 AWS Step Functions and Workflow Orchestration
4 Domain 3: Design High-Performing Architectures (24%)
3.1 EC2 Instance Types, Purchasing Options, and Placement Groups 3.2 Lambda, Serverless Compute, and Container Services 3.3 Amazon S3 - Storage Classes, Lifecycle, and Performance 3.4 Block and File Storage - EBS, EFS, and FSx 3.5 Database Services - RDS, Aurora, DynamoDB, and More 3.6 CloudFront, Route 53, and Global Accelerator 3.7 Data Ingestion and Transformation - Kinesis, Glue, and EMR
5 Domain 4: Design Cost-Optimized Architectures (20%)
4.1 Compute Cost Optimization — Right-Sizing, RIs, Savings Plans, and Spot 4.2 Storage Cost Optimization — S3 Tiers, EBS, and Data Transfer 4.3 Database Cost Optimization 4.4 AWS Cost Management and Monitoring Tools
6 VPC and Networking Deep Dive
5.1 VPC Architecture — Subnets, Route Tables, and Gateways 5.2 VPC Connectivity — Peering, Transit Gateway, and Direct Connect 5.3 Amazon API Gateway 5.4 CloudFormation and Infrastructure as Code 5.5 AWS PrivateLink and Endpoint Services
7 Migration, Transfer, and Hybrid Services
6.1 The 7 Rs of Cloud Migration 6.2 AWS Snow Family — Snowball Edge Devices 6.3 CloudWatch, CloudTrail, and AWS Config 6.4 Amazon Cognito and Identity Federation 6.5 AWS DataSync and Transfer Family
8 Serverless Architecture and Application Services
7.1 Serverless Architecture Patterns 7.2 Advanced SQS Patterns — DLQ, Backpressure, and FIFO 7.3 Analytics Services — Athena, OpenSearch, and QuickSight 7.4 Container Orchestration — ECS, EKS, and ECR
9 Advanced Topics and Exam Scenarios
8.1 Advanced IAM — Permission Boundaries, Federation, and Cross-Account 8.2 Caching Strategies and ElastiCache Patterns 8.3 Hybrid Architecture — DNS, Storage, and Compute 8.4 SAA-C03 Scenario Practice — Putting It All Together
1.1 IAM Fundamentals — Users, Groups, Roles, and Policies
Key Takeaways Explain This Topic AI
IAM is a global service — users, groups, roles, and policies are not Region-specific.
Follow the principle of least privilege: grant only the permissions needed to perform a task.
Use IAM roles (not access keys) for EC2 instances, Lambda functions, and cross-account access.
IAM policies are JSON documents with Effect, Action, Resource, and optional Condition elements.
The root user should be secured with MFA and never used for day-to-day operations.
Last updated: October 2026
Quick Answer: AWS Identity and Access Management (IAM) controls WHO can do WHAT on WHICH resources. Use users for human identities, groups to organize users, roles for temporary credentials (EC2, Lambda, cross-account), and policies to define permissions. Always apply least privilege and never use the root user for daily operations.
IAM Overview
AWS Identity and Access Management (IAM) is a global service that controls authentication (who are you?) and authorization (what may you do?) for every AWS Application Programming Interface (API) call. IAM itself is free — you pay only for the resources your identities consume. On the SAA-C03 exam (65 questions, 130 minutes, 720/1000 to pass), Domain 1 is the single largest block at 30%, so IAM mechanics are worth memorizing cold.
Key Characteristics
- Property Detail
- Scope Global — one IAM namespace spans all Regions
- Cost Free; charges come only from the resources accessed
- Consistency Eventually consistent — policy edits propagate in seconds
- Coverage Every signed AWS API request is authorized through IAM
- IAM Users vs. Groups
An IAM user is a long-lived identity for one person or application. A group is a container that attaches the same policies to many users at once.
- Concept Rules to Memorize
- User credentials Console password and/or access keys (Access Key ID + Secret Access Key)
- Group membership A user can belong to up to 10 groups ; groups cannot be nested
- Group as principal Groups cannot be referenced in resource-based policies or assume roles
- MFA Multi-Factor Authentication is per-user and strongly recommended
- IAM Roles
An IAM role is an identity with permissions that a trusted principal assumes to receive temporary credentials from the AWS Security Token Service (STS) . Roles are the secure-by-default answer whenever a workload — not a human — needs access.
When to Use Roles (high-yield)
- Scenario Mechanism
- EC2 needs S3/DynamoDB Attach an instance profile (role) to the instance
- Lambda needs other services Lambda execution role
- Cross-account access Role in the target account, assumed via sts:AssumeRole
- Corporate single sign-on Federated role via SAML 2.0 or OIDC
- How Assumption Works
A principal calls sts:AssumeRole .
STS checks the role's trust policy (who may assume it).
STS returns temporary credentials (access key, secret key, session token ).
Credentials expire after 15 minutes to 12 hours (configurable).
On the Exam: When an EC2 instance must reach S3, DynamoDB, or any AWS service, the answer is almost always "attach an IAM role." Storing long-term access keys on an instance is always wrong.
- IAM Policies
- Policies are JSON documents. Memorize the elements and evaluation order. {
- "Version": "2012-10-17",
- "Statement": [{
- "Sid": "AllowS3Read",
- "Effect": "Allow",
- "Action": ["s3:GetObject", "s3:ListBucket"],
- "Resource": ["arn:aws:s3:::my-bucket", "arn:aws:s3:::my-bucket/*"],
- "Condition": { "IpAddress": { "aws:SourceIp": "203.0.113.0/24" } }
- }]
- }
- Element Meaning Required
- Version Always 2012-10-17 Yes
- Effect Allow or Deny Yes
- Action API actions such as s3:GetObject Yes
- Resource Amazon Resource Names (ARNs) Yes
- Condition Optional keys (IP, MFA, tag, time) No
- Policy Types
AWS managed — prebuilt (e.g., ReadOnlyAccess ).
Customer managed — your reusable policies.
Inline — embedded in one entity (1:1).
Resource-based — attached to a resource (S3 bucket policy, KMS key policy).
Permission boundary — caps the maximum an identity can ever have.
Evaluation Logic (memorize)
Explicit Deny in any applicable policy → request denied. Deny always wins.
Organizations RCPs and SCPs must allow (if the account is in an organization).
Resource-based policy: within the same account, an Allow here can grant access even without an identity-based Allow , depending on the principal type (IAM role trust policies and KMS key policies must always allow explicitly).
Identity-based policy must allow (for most resources, an Allow in either the identity-based or a same-account resource-based policy is enough).
Permissions boundary and session policy must allow, if set.
Key Rule: If nothing explicitly allows an action, it is implicitly denied . An explicit Deny overrides every Allow.
The Root User
The root user is the account's founding email identity with unrestricted power. Best practices: enable MFA immediately, create no access keys for root, and reserve it for the handful of root-only tasks (changing account settings, closing the account). Use IAM Access Analyzer to surface unintended external access and CloudTrail to audit every call.
Identity-Based vs. Resource-Based Policies
The exam repeatedly tests the difference between the two policy attachment styles. An identity-based policy attaches to a user, group, or role and says "this identity may do X." A resource-based policy attaches to a resource — an S3 bucket policy, an SQS queue policy, a KMS key policy, or a Lambda function policy — and names a Principal that may act on that resource. Resource-based policies are the only practical way to grant cross-account access without first creating a role, and an S3 bucket policy is the standard answer when a question says "allow another AWS account to read this bucket."
When the request and the resource live in the same account , access is granted if either the identity-based policy or the resource-based policy allows it (and nothing denies it). When they live in different accounts , both sides must allow: the resource policy must name the external principal, and that principal's identity policy must permit the action. Memorizing this dual-allow rule prevents the classic mistake of fixing only one side of a cross-account grant.
IAM Identity Center and Federation
For human access at scale, AWS now steers customers toward IAM Identity Center (formerly AWS Single Sign-On) instead of individual IAM users. Identity Center connects an external identity provider — Active Directory, Okta, or any SAML 2.0 / OIDC source — and maps groups to permission sets that become roles in each account. The result is centralized, short-lived, MFA-protected console and CLI access with no long-lived keys to leak. On the exam, "hundreds of employees need least-privilege access across many accounts" points to IAM Identity Center with permission sets , not to creating an IAM user per person in every account.
Common IAM Exam Traps
Long-lived access keys on EC2 — always replaced by an instance-profile role.
Making a bucket public to solve an access problem — almost never correct; use a bucket policy or VPC endpoint policy instead.
Assuming an SCP grants access — it only caps; IAM still must allow.
Forgetting that Deny wins — an explicit Deny in any policy layer cannot be overridden by any Allow.
Believing IAM is Regional — it is global; a role works in every Region without duplication.