AWS Identity & Access Management (IAM)
Provides authentication and authorization boundaries across AWS workloads, eliminates hardcoded secrets through EC2 instance profiles and ECS task execution roles, and enforces least privilege.
AWS Container Placement
Regional / Global Managed Scope (Outside VPC Subnets)
Summary
Centrally manage access to AWS services and resources with granular JSON policies, temporary STS credentials, and role delegation.
When to Use (SAA-C03)
Always attach least-privilege IAM Roles to EC2/Lambda/ECS instead of embedding static AWS access keys; remember Explicit Deny always overrides Allow.
Allowed Ingress Connections & Ports
| Source Service | Protocol | Port | Architectural Rationale |
|---|---|---|---|
| EC2 | STS:AssumeRole | 443 | Instance profile token retrieval via IMDSv2 |
| LAMBDA | STS:AssumeRole | 443 | Serverless execution role initialization |
| ECS | STS:AssumeRole | 443 | Container task execution role credentials |
Allowed Egress Targets & Ports
| Target Service | Protocol | Port | Data Flow Rationale |
|---|---|---|---|
| S3 | HTTPS / SigV4 | 443 | Role-authorized object operations |
| DYNAMODB | HTTPS / SigV4 | 443 | Role-authorized NoSQL queries |
| SQS | HTTPS / SigV4 | 443 | Role-authorized message send/receive |
| KMS | HTTPS / SigV4 | 443 | Role-authorized key cryptographic operations |
Key Configuration Parameters & AWS Best Practices
| Parameter | Format / Example | Purpose & Rationale |
|---|---|---|
| Assume Role Trust Policy (assumeRolePolicy) (Required) | {"Version": "2012-10-17", "Statement": [{"Effect": "Allow", "Principal": {"Service": "ec2.amazonaws.com"}, "Action": "sts:AssumeRole"}]} | Specifies which principals (e.g. `ec2.amazonaws.com` or specific AWS accounts) can assume the role. Why: Without an authentic trust policy statement, no entity can assume the role or receive temporary credentials. |
| Role Name (roleName) (Required) | AppBackendEC2ServiceRole | The unique name identifier for the IAM role. Why: Identifies the role in AWS ARNs and CloudTrail audit records. |
| Permissions Boundary (permissionsBoundaryArn) | IAM Policy ARN | Sets the maximum allowable permissions boundary for the role. Why: Prevents delegated users from escalating privileges when creating new roles. |
| Max Session Duration (Seconds) | 3600 | The maximum duration in seconds for an assumed role session. Why: Limits exposure window of temporary STS credentials. |
Practice Labs Using AWS Identity & Access Management
SaaS Container Platform: EKS Worker Node VPC CNI IPv4 Exhaustion
Attach secondary CIDR 100.64.0.0/16 to VPC and provision dedicated pod subnets and ECR interface endpoints.…
SAA-C03-GITHUB-OIDC-CICDEnterprise Cloud Security: GitHub Actions Keyless OIDC CI/CD to Private VPC
Replace static IAM credentials with GitHub OIDC Identity Provider and IAM Role with AssumeRoleWithWebIdentity …
Frequently Asked Questions
Where does AWS Identity & Access Management live inside an AWS VPC architecture?
Valid container placement: Regional / Global Managed Scope (Outside VPC Subnets). Provides authentication and authorization boundaries across AWS workloads, eliminates hardcoded secrets through EC2 instance profiles and ECS task execution roles, and enforces least privilege.
When should I use AWS Identity & Access Management on the AWS SAA-C03 exam?
Always attach least-privilege IAM Roles to EC2/Lambda/ECS instead of embedding static AWS access keys; remember Explicit Deny always overrides Allow.
Can I simulate AWS Identity & Access Management packet routing without an AWS account?
Yes. CloudTracer simulates AWS Identity & Access Management along with 53 AWS services directly in your browser and exports production Terraform HCL.