Study guide

8.1 Advanced IAM — Permission Boundaries, Federation, and Cross-Account

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

8.1 Advanced IAM — Permission Boundaries, Federation, and Cross-Account

Key Takeaways Explain This Topic AI

A permission boundary is a managed policy that caps the MAXIMUM permissions an IAM user or role can ever have — effective permissions are the intersection of the identity policy and the boundary.

Service Control Policies (SCPs) live in AWS Organizations and cap permissions for entire accounts/OUs; they never GRANT access, only filter it, and do not apply to the management account.

Cross-account access via IAM roles uses a trust policy in the target account plus sts:AssumeRole from the source; STS returns temporary credentials (default 1 hour, max 12 hours).

Resource-based policies (S3 bucket, SQS, SNS, KMS key, Lambda) grant cross-account access while the caller KEEPS its original identity — no role assumption needed.

IAM Access Analyzer finds resources shared externally and can generate least-privilege policies from CloudTrail; ExternalId in a trust policy defeats the confused-deputy problem for third parties.

Last updated: June 2026

Quick Answer: A permission boundary caps the max permissions a user/role can have; effective access = identity policy INTERSECT boundary. Service Control Policies (SCPs) cap whole accounts/OUs in AWS Organizations but never grant. Cross-account access uses an IAM role (trust policy + sts:AssumeRole ) or a resource-based policy (caller keeps its identity). IAM Identity Center delivers SSO across many accounts. IAM Access Analyzer flags external sharing and builds least-privilege policies.

Permission Boundaries

A permission boundary is a managed policy attached to an IAM user or role that defines the ceiling on permissions. It never grants access by itself — it only limits what an identity policy can effectively allow. The exam loves the privilege-escalation scenario: let developers create roles for Lambda or EC2 without letting them mint an admin role.

The intersection rule

Effective permissions = Identity (or session) policy AND Permission Boundary . An action is allowed only if BOTH allow it, with no explicit Deny anywhere (an explicit Deny in any policy always wins).

  • Identity Policy Grants Permission Boundary Allows Effective Permissions
  • s3:* , ec2:* , rds:* s3:* , ec2:* s3:* , ec2:* (rds blocked)
  • s3:GetObject s3:* , ec2:* s3:GetObject
  • ec2:TerminateInstances s3:* only None (ec2 not in boundary)
  • s3:* (with explicit Deny s3:DeleteObject ) s3:* s3:* except DeleteObject
  • Boundaries vs SCPs vs identity policies

This distinction is a frequent trap. SCPs are an AWS Organizations feature; they apply to entire accounts or Organizational Units (OUs) and filter the permissions of every IAM principal in those accounts (root user included for member accounts, but SCPs do not restrict the management account ). A permission boundary is attached to a single user or role. An identity policy is what actually grants. For a request to succeed it must pass all layers: SCP allows it, the boundary allows it, the identity policy allows it, and no Deny blocks it.

Common Trap: SCPs and permission boundaries NEVER grant permissions. If an SCP is the only thing 'allowing' an action, the principal still has zero access until an identity or resource policy grants it.

IAM Identity Center (formerly AWS SSO)

IAM Identity Center centralizes workforce sign-in across every account in an AWS Organization and into SAML business apps.

  • Feature Detail
  • Single sign-on One login to all member accounts and to SAML 2.0 apps (Salesforce, Slack)
  • Identity source Built-in directory, AWS Managed Microsoft AD / AD Connector, or external IdP (Okta, Entra ID)
  • Permission sets Reusable bundles of IAM policies mapped to users/groups per account
  • ABAC Pass directory attributes as session tags for attribute-based access control

On the Exam: 'Employees need SSO to 50 accounts by job function' → IAM Identity Center with permission sets. 'A workload in account A needs temporary access to account B' → cross-account IAM role.

  • Cross-Account Access
  • Method 1 — IAM roles (most common, all services)

Target account creates a role whose trust policy lists the source account/principal as a trusted entity (the Principal ).

Source principal calls sts:AssumeRole on that role.

AWS Security Token Service (STS) returns temporary credentials (default 1 hour, configurable 15 min – 12 hours via DurationSeconds / MaxSessionDuration ).

The caller uses those credentials and is logged in the target account's CloudTrail as the role.

Method 2 — Resource-based policies (only some services)

S3 bucket, SQS queue, SNS topic, KMS key, and Lambda function policies can name an external account directly. The caller keeps its own identity (no AssumeRole ), so CloudTrail in the target account records the original principal.

  • Feature IAM Role Resource-Based Policy
  • Identity after access Assumes a new role identity Keeps original identity
  • CloudTrail in target Logged as the role Logged as original principal
  • Service support All services S3, SQS, SNS, KMS, Lambda only
  • Confused-deputy and ExternalId

When you grant a third-party SaaS (e.g., a monitoring vendor) a role, set an ExternalId condition in the trust policy. The vendor must pass that unique value on AssumeRole , preventing another customer of the same vendor from tricking the vendor into accessing your account — the confused-deputy problem.

IAM Access Analyzer

  • Capability Detail
  • External access findings Flags S3 buckets, IAM roles, KMS keys, Lambda, SQS shared outside your account/Org
  • Policy validation Lints policies against grammar and security best-practice checks
  • Policy generation Builds least-privilege policies from CloudTrail activity history
  • Unused access Surfaces unused roles, access keys, and permissions

On the Exam: 'Find S3 buckets or roles reachable from outside the account' → IAM Access Analyzer external findings. 'Generate a least-privilege policy from what the role actually did' → Access Analyzer policy generation from CloudTrail.

Temporary Credentials and Federation

The SAA-C03 exam consistently prefers temporary credentials over long-lived access keys . Several mechanisms all flow through STS:

IAM roles for EC2 (instance profile): the instance retrieves rotating credentials from the metadata service — never hard-code keys on an instance.

Web identity federation / Amazon Cognito: mobile or web users sign in with an external identity provider (Google, Apple, a SAML/OIDC IdP) and Cognito identity pools exchange that token for temporary AWS credentials scoped to a role.

SAML 2.0 federation: enterprise users authenticate against the corporate IdP and assume a role via AssumeRoleWithSAML .

  • Audience Mechanism Result
  • EC2 / Lambda / ECS task IAM role attached to the compute Auto-rotated temporary credentials
  • Mobile/web app users Cognito identity pool + IdP Short-lived role credentials per user
  • Corporate workforce IAM Identity Center or SAML federation SSO into accounts via permission sets/roles

Common Trap: 'A mobile app needs to upload directly to S3 for millions of users' → Cognito identity pools issuing temporary credentials, NOT one shared IAM user with embedded keys. Embedding access keys in an app is an automatic wrong answer.