Study guide
10.1 Advanced IAM Policies, Roles & Policy Conditions
AWS Certified CloudOps Engineer – Associate SOA-C03
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: Monitoring & Observability Infrastructure
1.1 Configuring Workload Observability 1.2 CloudWatch Agent Architecture & Deployment 1.3 Metric Alarms, Anomaly Detection & Composite Alarms
2 Chapter 2: Alarms, Dashboards & Event-Driven Remediation
2.1 CloudWatch Dashboards & Multi-Account Visibility 2.2 Notification Architecture & Alarm Invocation 2.3 Amazon EventBridge Rules, Event Buses & Troubleshooting 2.4 Automated Remediation with Systems Manager & Lambda
3 Chapter 3: Performance Optimization for Compute, Storage & Databases
3.1 EC2 & Compute Performance Optimization 3.2 Amazon EBS Performance Metrics & Volume Tuning 3.3 S3 Performance Strategies & Data Transfer 3.4 Shared Storage (EFS/FSx) & Database Performance
4 Chapter 4: Compute & Database Scalability and Elasticity
4.1 EC2 Auto Scaling Policies & Elasticity 4.2 Auto Scaling Advanced Operations: Warm Pools & Lifecycle Hooks 4.3 Dynamic Scalability Through Caching 4.4 Managed Database Scaling: RDS, Aurora & DynamoDB
5 Chapter 5: High Availability, Fault Tolerance & Load Balancing
5.1 Elastic Load Balancing (ALB/NLB) Configuration & Troubleshooting 5.2 Route 53 Health Checks & DNS Failover 5.3 Multi-AZ Architecture & Fault-Tolerant Deployments
6 Chapter 6: Backup, Data Protection & Disaster Recovery
6.1 Centralized Backup Automation & AWS Backup 6.2 Database Restore Strategies & RTO/RPO Management 6.3 Storage Versioning, Replication & Immutability 6.4 Disaster Recovery Patterns & Multi-Region Resilience
7 Chapter 7: Infrastructure as Code with CloudFormation & AWS CDK
7.1 CloudFormation Foundations & Resource Modeling 7.2 Managing Stacks, Drift Detection & Change Sets 7.3 Infrastructure as Code with AWS CDK 7.4 Identifying & Remediating Deployment Failures
8 Chapter 8: Multi-Account Provisioning, Containers & Third-Party IaC
8.1 Golden Images with EC2 Image Builder & Amazon ECR 8.2 Multi-Account & Multi-Region Resource Sharing 8.3 Deployment Strategies & Container Deployments 8.4 Third-Party Automation with Terraform & Git Workflows
9 Chapter 9: Systems Manager & Event-Driven Operations Automation
9.1 AWS Systems Manager Core Management & Run Command 9.2 Systems Manager Patch Manager & Session Manager 9.3 Event-Driven Operations Automation
10 Chapter 10: Identity, Access Management & Governance
10.1 Advanced IAM Policies, Roles & Policy Conditions 10.2 Auditing Access with CloudTrail Lake & IAM Access Analyzer 10.3 Multi-Account Security: Organizations, SCPs & Identity Center 10.4 Compliance Enforcement with AWS Config & Conformance Packs
11 Chapter 11: Data Security, Encryption & Vulnerability Management
11.1 Data Classification & Amazon S3 Security 11.2 Encryption at Rest with AWS Key Management Service (KMS) 11.3 Encryption in Transit with AWS Certificate Manager (ACM) 11.4 Secrets Management & Centralized Security Findings
12 Chapter 12: VPC Architecture, Endpoints & Network Protection
12.1 VPC Core Architecture, Subnetting & High Availability NAT 12.2 Private Network Connectivity: VPC Endpoints & Peering 12.3 Network Protection & Edge Security Auditing
13 Chapter 13: DNS, Route 53 Routing & Content Delivery
13.1 DNS Architecture & Route 53 Resolver for Hybrid Clouds 13.2 Route 53 Advanced Routing Policies & Query Logging 13.3 Global Content & Service Distribution: CloudFront & Global Accelerator
14 Chapter 14: Network Troubleshooting, Traffic Analysis & Hybrid Connectivity
14.1 VPC Configuration Troubleshooting & Analysis Tools 14.2 Network Traffic Analysis: VPC Flow Logs & Log Analytics 14.3 CloudFront Caching & Hybrid Connectivity Troubleshooting
10.1 Advanced IAM Policies, Roles & Policy Conditions
Key Takeaways Explain This Topic AI
AWS IAM policy evaluation follows a strict decision hierarchy: an explicit deny always trumps an allow, a default deny applies if no allow exists, and multiple matching allow statements form a permissive union.
Permissions boundaries establish maximum allowable permissions for IAM entities without granting access directly, providing a critical guardrail when delegating IAM role or user administration.
IAM Roles vend short-lived temporary credentials via AWS STS; IRSA in Amazon EKS leverages OIDC federation and service account annotations to eliminate static node-level credentials.
Cross-account role assumption by third-party SaaS vendors requires the sts:ExternalId condition in the role trust policy to effectively prevent the confused deputy vulnerability.
Advanced condition keys (aws:PrincipalOrgID, aws:SecureTransport, aws:RequestedRegion, and aws:PrincipalTag) enforce organization-wide boundaries, transport encryption, geo-fencing, and Attribute-Based Access Control (ABAC).
Last updated: September 2026
10.1 Advanced IAM Policies, Roles & Policy Conditions
CloudOps Blueprint Focus: The AWS Certified CloudOps Engineer – Associate (SOA-C03) exam tests your ability to evaluate complex IAM policy logic, implement permissions boundaries to prevent privilege escalation, configure temporary credentials via AWS STS and EKS IRSA, and enforce fine-grained policy conditions including external IDs and Attribute-Based Access Control (ABAC).
IAM Policy Structure & Evaluation Logic
AWS Identity and Access Management (IAM) controls authentication and authorization for every AWS API call by evaluating an authorization request context containing the principal, action, resource, environment attributes, and tags.
An IAM policy document contains statements built from five core elements:
Effect: Sets the outcome to Allow or Deny .
Principal: Specifies the entity granted or denied access. Required in resource-based policies and trust policies, but omitted in identity-based policies.
Action: Lists specific service API calls (e.g., s3:GetObject , ec2:RunInstances ).
Resource: Identifies target resources using Amazon Resource Names (ARNs) or wildcard * .
Condition: Dictates criteria under which the statement applies using key-value operators.
Evaluation Workflow
Default Deny: All requests begin implicitly denied.
Explicit Deny Precedence: If any applicable statement contains an explicit Deny , evaluation terminates immediately with a final Deny , overriding all allows.
Union of Allows: If no explicit deny exists, at least one statement must explicitly Allow the request. Matching allow statements form a permissive union.
Absence of Allow: If no explicit deny and no explicit allow match, the request remains denied.
Policy Types: Identity-Based, Resource-Based & Permissions Boundaries
Policy Type Attached To Principal Required? Cross-Account Characteristics
Identity-Based (Managed) IAM Users, Groups, Roles No Requires assuming a role in the target account.
Identity-Based (Inline) Single IAM User or Role No Tightly coupled; deleted if the parent entity is deleted.
Resource-Based S3, KMS, SQS, Secrets Manager Yes Permits direct resource access without switching roles.
Permissions Boundary IAM Users, Roles No Defines maximum allowable permissions ceiling; grants nothing.
Customer managed policies provide versioning (up to 5 versions), rollback capabilities, and reusability. AWS managed policies are maintained by AWS but often grant broad privileges. Inline policies embed directly into a single entity and should be reserved for strict 1:1 exception mappings.
Resource-based policies attach directly to AWS resources, allowing principals from external accounts to access resources directly without assuming a cross-account role. For AWS KMS, cross-account access requires explicit permission in both the identity policy and the KMS key policy, unless the key policy delegates authority to the external account root.
Permissions Boundaries
A permissions boundary is an IAM managed policy that sets the maximum permissions an identity-based policy can grant. It does not grant permissions on its own; effective permissions are the intersection of the identity policy and the boundary. CloudOps teams use boundaries to safely delegate IAM role creation to developers without risking privilege escalation. Developers are granted iam:CreateRole and iam:PutRolePolicy constrained by a condition requiring that all created roles must have the approved boundary attached.
IAM Roles, Temporary Credentials & Advanced Federation
Enterprise operations standardize on IAM Roles that vend short-lived temporary credentials via AWS Security Token Service (STS) . Temporary credentials consist of an Access Key ID, Secret Access Key, and Session Token, valid for 15 minutes to 12 hours.
Core STS Operations & EC2 Instance Profiles
sts:AssumeRole : Exchanges IAM identity or service context for temporary role credentials.
sts:AssumeRoleWithWebIdentity : Federates OIDC JSON Web Tokens (JWTs) from Kubernetes or GitHub Actions.
sts:AssumeRoleWithSAML : Exchanges corporate SAML 2.0 assertions for AWS credentials.
EC2 Instance Profiles: Deliver automatically rotated credentials to EC2 instances via the Instance Metadata Service (IMDSv2) at http://169.254.169.254/latest/meta-data/iam/security-credentials/<role-name> .
Amazon EKS: IAM Roles for Service Accounts (IRSA)
Attaching broad IAM roles to EC2 worker nodes violates least privilege because all pods on the node inherit those permissions. IRSA provides pod-level IAM isolation:
An EKS cluster is associated with an IAM OIDC Identity Provider.
A Kubernetes ServiceAccount is annotated with eks.amazonaws.com/role-arn .
An EKS mutating admission webhook injects AWS_ROLE_ARN and AWS_WEB_IDENTITY_TOKEN_FILE into matching pods.
The AWS SDK calls sts:AssumeRoleWithWebIdentity using the projected pod token, restricting permissions strictly to that microservice.
Cross-Account Role Assumption & Confused Deputy Mitigation
When third-party SaaS vendors manage AWS infrastructure across multiple clients, a malicious client could trick the SaaS vendor into accessing another customer's resources (the confused deputy problem). To eliminate this risk, the customer's role trust policy must require the sts:ExternalId condition key. The vendor assigns a unique External ID string per customer, ensuring the vendor supplies the correct client token during sts:AssumeRole .
Advanced Policy Condition Keys & ABAC
Advanced condition keys enforce contextual guardrails:
aws:PrincipalOrgID : Verifies that the calling principal belongs to a specific AWS Organization (e.g., o-1234567890 ), simplifying multi-account S3 bucket policies.
aws:SourceIp : Restricts API execution to corporate IP CIDRs. Caveat: When an AWS service acts on a user's behalf (such as CloudFormation provisioning resources), service calls fail unless combined with aws:ViaAWSService or service principal exemptions.
aws:SecureTransport : Enforces TLS by explicitly denying actions when {"Bool": {"aws:SecureTransport": "false"}} .
aws:RequestedRegion : Geo-fences API requests to approved AWS Regions.
aws:MultiFactorAuthPresent : Mandates active MFA for destructive actions like terminating EC2 instances or deleting snapshots.
Attribute-Based Access Control (ABAC): Compares tags on the principal ( aws:PrincipalTag/Department ) with tags on the resource ( aws:ResourceTag/Department ). ABAC scales authorization dynamically without requiring continuous policy edits as new employees or resources are provisioned.