CertNote/ Commute Study Notes
Roadmap
KOEN
CLF-C02 · FoundationalCloud Practitioner - Foundational
DVA-C02 · AssociateDeveloper - Associate
SAA-C03 · AssociateSolutions Architect - Associate
SOA-C02 · AssociateCloudOps Engineer - Associate
SAP-C02 · ProfessionalSolutions Architect - Professional
  • Week 1
    • 1.The Game Called the SAP Exam: Hands-On Techniques for Decomposing Scenarios
    • 2.IAM, STS, and Federation: Splitting the Word "Permission" into Six Layers
    • 3.The Anatomy of a VPC: What Route Tables Really Decide
    • 4.Four Compute Pillars in Depth: Revisiting Nitro, EBS, ELB, and Auto Scaling Through a Pro Lens
    • 5.Week 1 Integration: When IAM, VPC, and EC2 Meet in a Single Scenario
  • Week 2
  • Week 3
  • Week 4
  • Week 5
  • Week 6
  • Week 7
  • Week 8
  • Week 9
  • Week 10
  • Week 11
  • Week 12
  • Week 13
  • Week 14
  • Week 15
  • Week 16
DOP-C02 · ProfessionalDevOps Engineer - Professional
Linux Master 2 · 2급KAIT Linux Master - Level 2
SCS-C03 · SpecialtySecurity - Specialty
Linux Master 1 · 1급KAIT Linux Master - Level 1
MLA-C01 · AssociateMachine Learning Engineer - Associate
AIF-C01 · FoundationalAI Practitioner - Foundational
DEA-C01 · AssociateData Engineer - Associate
MLS-C01 · SpecialtyMachine Learning - Specialty
SQLD · 개발자SQL Developer (SQLD)

© CertNote · 주간랩스

  • About
  • Changelog
  • Contact
  • Terms
  • Privacy
← SAP-C02/Week 1/Day 5

Based on the SAP-C02 exam guide·Report an error

SAP-C02· ProWeek 1 · Day 5~36 min read

Day 5 - Week 1 Integration: When IAM, VPC, and EC2 Meet in a Single Scenario

On the Pro exam, questions that ask about only a single service are practically nonexistent. Whatever scenario unfolds, IAM (who is accessing), VPC (where it flows), and EC2/EBS/ELB (what processes that traffic) appear simultaneously. So today we revisit the three areas we studied separately during the week in the way they meet within a single scenario. This is the real way of thinking that works on the exam floor.

Today's article has three parts.

  1. 40 one-line summaries of Week 1: facts that must surface within 0.5 seconds in the exam room.
  2. The 3-layer method: the hands-on technique of decomposing scenarios into IAM ⇒ VPC ⇒ Compute.
  3. 12 scenario questions: Pro difficulty, 30 minutes of solving time.

Practice these three as one bundle, and when you meet a scenario in the exam room your hands will move first. The "5-step decomposition" from Day 1 fires in your head within 5 seconds, and those 5 steps flow again into the 3 layers of IAM-VPC-Compute.

40 One-Line Summaries of Week 1

Exam Strategy (1-5)

  1. SAP-C02 = 75 questions / 180 minutes / 750 to pass; ESL +30 minutes can be requested (210 minutes total).
  2. 5-step scenario decomposition: WHO · WHAT · WHY · CONSTRAINTS · KEYWORD. The adjective in the last sentence decides the answer.
  3. Four elimination patterns for the 4 options: over-engineering / under-engineering / build-it-yourself / wrong combination.
  4. The 3-2-2 rule: under 3 minutes per question, change your answer at most 2 times, flag if unsolved within 2 minutes.
  5. The first-instinct fallacy — statistically, changed answers are wrong more often. Without solid grounds, keep your first intuition.

IAM·STS·Federation (6-15)

  1. 6 layers of permission evaluation: SCP → Permission Boundary → Identity Policy → Resource Policy → Session Policy → VPC Endpoint Policy. If any one of the 6 layers denies, it's blocked; all must allow to pass.
  2. An explicit deny beats every allow — a single explicit Deny is the end.
  3. Cross-account access requires Allow on both sides (Trust Policy + Resource Policy or Identity Policy).
  4. SCPs and Permission Boundaries have deny-only semantics — they grant no permissions, they only set a ceiling.
  5. The 5 STS operations: AssumeRole / AssumeRoleWithSAML / AssumeRoleWithWebIdentity / GetFederationToken / GetSessionToken.
  6. ExternalId prevents the confused deputy attack — mandatory for SaaS third-party access, specified in the Trust Policy.
  7. GitHub Actions → AWS uses OIDC + AssumeRoleWithWebIdentity (no long-lived keys needed); restrict repo/branch via the sub claim in the Trust Policy.
  8. Multi-account SSO is IAM Identity Center + Permission Sets, with automatic sync via SCIM (RFC 7644).
  9. ABAC is tag-based — matching aws:PrincipalTag/Project ↔ aws:ResourceTag/Project prevents policy explosion.
  10. IAM Access Analyzer automatically detects external access using Zelkova (SMT-based formal verification) from Microsoft Research.

VPC·Network (16-26)

  1. RFC 1918 private IPs: 10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16. Range /16–/28; prevent company-wide IP conflicts with IPAM.
  2. 5 reserved IPs per subnet: .0 (network) / .1 (router) / .2 (DNS) / .3 (reserved) / .255 (broadcast).
  3. NAT Gateway is AZ-local → one per AZ for availability. A single NAT means all outbound is blocked when that AZ dies.
  4. SGs are stateful (return traffic auto-allowed), NACLs are stateless (explicit both ways).
  5. NACL ephemeral ports: Linux 32768-60999, Windows 49152-65535; the safe range is 1024-65535.
  6. S3 and DynamoDB use Gateway Endpoints (free, prefix list in the Route Table); everything else uses Interface Endpoints ($0.01/hour + data).
  7. PrivateLink: a SaaS exposes its service behind an NLB as an Endpoint Service, no bidirectional routing.
  8. SG ID references only work within the same VPC and Peered VPCs; Transit Gateway allows IP CIDR references only.
  9. VPC Flow Logs record ENI 5-tuples + outcomes, no payload. Traffic Mirroring captures payload.
  10. Transit Gateway is BGP-based hub-and-spoke, up to 5000 VPCs, segmentation per route table.
  11. Direct Connect is dedicated (dedicated line) vs hosted (partner-shared), with 3 VIF types (Private/Public/Transit).

EC2·EBS·ELB·ASG (27-40)

  1. Nitro System: ASIC-based card virtualization, under 1% overhead. Network, EBS, Security, and Hypervisor on separate cards.
  2. Graviton (g suffix) is ARM Neoverse-based, 20-40% price-performance advantage over equivalent x86. Multi-arch containers mandatory.
  3. Inferentia/Trainium ASICs cut costs 60-70% versus GPU for LLM inference/training.
  4. gp3 provisions IOPS and size independently (20% cheaper than gp2), but no burst.
  5. io2 Block Express is NVMe-oF-based sub-ms latency, 256K IOPS, r5b/x2idn only.
  6. EBS is AZ-local + 3 synchronous replicas; other AZs only via snapshot.
  7. EBS Multi-Attach: io1/io2 + clustered filesystem (GFS2/OCFS2/OracleRAC) + 16 instances.
  8. Only NLB has static IPs + client IP preservation + millions of packets per second (flow-hash-based ECMP).
  9. ALB has direct Cognito integration (X-Amzn-Oidc-Data header), first-class gRPC support.
  10. Warm Pool pre-boots stopped instances, cold start 5 min → 30 sec.
  11. Mixed Instances Policy + price-capacity-optimized is the Spot standard.
  12. Spot averages 70% off, reclaimed after a 2-minute warning, diversify across families.
  13. Placement Groups: Cluster (low-latency HPC) / Spread (isolation, 7/AZ) / Partition (HDFS/Cassandra rack-aware).
  14. Lifecycle Hook default heartbeat is 1 hour, max 48 hours; calling complete-lifecycle-action is mandatory.

The 3-Layer Method: IAM ⇒ VPC ⇒ Compute

When solving Pro scenarios, checking the 3 layers in order reveals missing elements.

┌──────────────────────────────────────────────────┐
│ Layer 1: IAM   "Who is accessing?"               │
│   - SCP / Permission Boundary / IAM / Resource   │
│   - Federation (SAML/OIDC), STS, ABAC            │
│   - Cross-Account Role + ExternalId              │
├──────────────────────────────────────────────────┤
│ Layer 2: VPC   "Where does it flow?"             │
│   - VPC CIDR, Subnet, Route Table                │
│   - SG (stateful) + NACL (stateless)             │
│   - VPC Endpoint (Gateway/Interface), PrivateLink│
│   - Transit Gateway, Direct Connect, VPN         │
├──────────────────────────────────────────────────┤
│ Layer 3: Compute  "What processes it?"           │
│   - EC2 family / pricing / Nitro / Graviton      │
│   - EBS type (gp3/io2BE/st1), Snapshot, FSR      │
│   - The 4 ELBs (ALB/NLB/GLB/CLB)                 │
│   - ASG (Target/Step/Predictive/Warm Pool)       │
└──────────────────────────────────────────────────┘

💡 Related theory: This 3-layer approach is a direct implementation of "Complete Mediation" and "Defense in Depth" from Saltzer and Schroeder's 8 security principles (1975). Every request passes through three gates: (1) permission check at IAM, (2) network isolation at VPC, (3) workload execution at Compute. If one gate is breached, another gate blocks. The Capital One incident breached the IAM gate via SSRF, but if a VPC Endpoint Policy had also been applied, the S3 access would have been blocked.

🔍 Deeper dive: Between the three layers there is boundary translation. The IAM Principal ARN turns into a VPC Source IP (which appears externally as the same IP when going through NAT), and at Compute it is translated back into the IAM Role from instance metadata. Information gets blurred during these translations, so when tracing with CloudTrail in multi-account environments you must look at user-agent + source IP + role session name all together. With a single variable, you may not know who did it.

A Hands-On Example of Scenario Decomposition

Scenario: "A global pharmaceutical company runs 80 accounts in AWS Organizations. The research division uses EC2 + RDS PostgreSQL to handle clinical trial data. Under FDA 21 CFR Part 11 regulations, all data access must have an audit trail, and the data must stay only in ap-northeast-2. Additionally, external SaaS providers (Veeva, Medidata) must read some of the data, and the use of access keys is prohibited. What is the most appropriate architecture?"

5-step decomposition + 3-layer mapping:

  1. WHO: global pharma, 80 accounts, research division + external SaaS (Veeva/Medidata).
  2. WHAT: EC2 + RDS PostgreSQL, clinical trial data.
  3. WHY: FDA 21 CFR Part 11, data sovereignty (ap-northeast-2).
  4. CONSTRAINTS: all access audited, access key usage prohibited.
  5. KEYWORD: regulation + multi-account + SaaS access + key avoidance.

→ 3-layer answer:

  • IAM layer: SCP denies regions other than ap-northeast-2. External SaaS uses Cross-Account Role + ExternalId (avoiding access keys). Unify CloudTrail across 80 accounts with an Org Trail. Encrypt data with a KMS custom CMK + Key Policy.
  • VPC layer: VPC Endpoints (S3, RDS, KMS) + Endpoint Policies to block external flows. External SaaS exposed via PrivateLink behind an NLB. Block outbound internet with NACLs/SGs (no internet traversal).
  • Compute layer: EC2 enforces IMDSv2, EBS is KMS-encrypted, RDS is Multi-AZ + automatic backups + 35-day retention. Export RDS audit logs to CloudWatch Logs.

Almost all of Week 1's learning is packed into this one scenario. The standard solving flow in the exam room is for your hand to draw the 3 layers automatically and fill each layer with keywords.

📝 Practice Questions

Click a choice to reveal the answer and explanation.

Question 1

A company operates 100 accounts. The security team wants to "block root user logins entirely in the production OU, and also block IAM calls without MFA." The most suitable method?

Question 2

A global SaaS operates in us-east-1 and is expanding to eu-west-1. EU user data must stay in the EU per GDPR. To guarantee data isolation while keeping a single codebase?

Question 3

A fintech wants to enforce that no EC2 can use any region other than us-east-1, for PCI-DSS certification. To minimize operational burden?

Question 4

A company accesses S3 from EC2. Traffic goes through a NAT Gateway, costing $30,000/month. A PCI-DSS audit also flagged that "S3 traffic traverses the internet." How to solve?

Question 5

A media company runs global game matchmaking (WebSocket). It exposes static IPs externally, needs failover within seconds on regional failure, and handles 1 million packets per second. The suitable combination?

Question 6

A company deploys to AWS Lambda from GitHub Actions. The security team requires "no long-lived AWS Access Keys stored in GitHub Secrets." How to solve?

Question 7

A company runs 100 EC2 instances for 4 hours for a nightly ETL batch (stateless, restartable). Minimize cost + meet the SLA (complete by 09:00 the next day).

Question 8

A company applies authentication behind an ALB. The backend (Node.js) wants almost no auth code and just wants to receive user info. The most suitable method?

Question 9

A company runs RDS MySQL in us-east-1 and wants to build DR in ap-northeast-2. RPO within 1 minute, RTO within 5 minutes. The most suitable solution?

Question 10

A SaaS wants to make its service usable via private IPs inside customer VPCs. The standard pattern?

Question 11

A company has an AD with 200 employees. SSO access to 80 accounts in AWS Organizations. When an employee leaves, permissions must be revoked automatically across all accounts. The most suitable solution?

Question 12

There are 3 Private Subnets across Multi-AZ, calling external APIs. To secure availability while minimizing cost, how should NAT Gateways be placed?

Wrapping Up

Week 1 reviewed the grammar of the exam and the four core SAA areas (IAM, VPC, EC2, ELB) at Pro depth. When the 40 one-line summaries and the 3-layer method work in the exam room, your hands automatically start decomposing even a scenario you've never seen.

From Week 2 we enter multi-account architecture (Organizations, SCP, Control Tower, Identity Center) — covered in earnest only at the SAP level. It accounts for 26% of Domain 1, so it's the biggest ROI. Solve today's 12 scenario questions once more, and for the ones you got wrong, apply the decomposition method to see where you went wrong. The moment your hand draws the 5 boxes first in the exam room is the signal of a pass.

PreviousFour Compute Pillars in Depth: Revisiting Nitro, EBS, ELB, and Auto Scaling Through a Pro LensWeek 1 · Day 4Next AWS Organizations: A New Unit of Thought for Multi-Account ArchitectureWeek 2 · Day 1

Official references

  • SAP-C02 official exam page(opens in a new tab)
  • Amazon VPC documentation(opens in a new tab)
  • AWS IAM documentation(opens in a new tab)
  • Elastic Load Balancing documentation(opens in a new tab)
  • Amazon EC2 documentation(opens in a new tab)
  • Amazon RDS · Aurora documentation(opens in a new tab)

On this page

  • 40 One-Line Summaries of Week 1
  • Exam Strategy (1-5)
  • IAM·STS·Federation (6-15)
  • VPC·Network (16-26)
  • EC2·EBS·ELB·ASG (27-40)
  • The 3-Layer Method: IAM ⇒ VPC ⇒ Compute
  • A Hands-On Example of Scenario Decomposition
  • 12 Scenario Questions (Pro Difficulty)
  • Wrapping Up