Cert Notes/ Commute Study Notes
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
DOP-C02 · ProfessionalDevOps Engineer - Professional
  • Week 1
    • 1.DevOps as an Operating Model: The Five Axes of CALMS and the Truth DORA Proved Through Measurement
    • 2.Well-Architected Framework: Rereading It Through the Six Lenses of DevOps
    • 3.The AWS DevOps Tool Map: The Code* Series and the Real Picture Beyond It
    • 4.Multi-Account Strategy: The Real Picture of Organizations, Control Tower, and IAM Identity Center
    • 5.Week 1 Wrap-Up: Cementing the DevOps Thinking Frame with Scenarios
  • Week 2
    • 1.CodeCommit Deep Dive: What Changes When Git Hosting is Integrated with IAM
    • 2.GitHub Actions ↔ AWS OIDC: Eliminating Static Keys Permanently Through Federation
    • 3.CodeArtifact and Supply Chain Security: When Dependencies Become Attack Surface
    • 5.Week 2 Synthesis: DevSecOps Thinking Framework From Source Control to Code Signing
  • Week 4
    • 1.In-place vs Blue/Green, AppSpec: The Physics of Deployment Strategies
    • 2.EC2/On-Prem Deployment + Auto Scaling Integration: The Intersection of Instance Lifecycle and Deployment
    • 3.Lambda Deployment: Linear/Canary/AllAtOnce and the Math of Aliases
    • 4.ECS Blue/Green + CodeDeploy Traffic Shift: The Logic of Two Target Groups
    • 5.Week 4 Review: Integrated Scenarios in CodeDeploy Deployment Strategies
  • Week 5
    • 1.CodePipeline Architecture: Understanding Why Stage, Action, and Artifact Were Designed This Way
    • 2.Multi-Account Pipeline: Why Cross-Account IAM Is Required
    • 3.Action Providers: How Lambda, Step Functions, and Manual Approval Extend the Pipeline
    • 4.Dynamic Pipeline: V2 Variable System, Trigger Filters, and Execution Mode Design
    • 5.Week 5 Review: CodePipeline Integration Scenarios
  • Week 6
    • 1.ECR: Solving the Problems that Container Image Registries Must Solve
    • 2.ECS Automatic Deployment: From Task Definition Update to Auto Scaling
    • 3.EKS CI/CD: Why GitOps Was Born, and How ArgoCD and Flux Changed Kubernetes
    • 4.App Runner and ECS Copilot: The Spectrum of Container Operations Abstraction
    • 5.Week 6 Review + 12 Scenario Practice Problems
  • Week 7
    • 1.Serverless CI/CD: Lambda, SAM, and Canary Deployments
    • 2.Lambda Permissions, Layers, and Container Images
    • 3.API Gateway and Serverless Integrations
    • 4.X-Ray and CloudWatch for Serverless Observability
    • 5.Week 7 Review: Serverless CI/CD Summary
  • Week 8
    • 1.CloudFormation Advanced: Nested·Cross-Stack and the Deep Story of Modularization
    • 2.StackSets: The Deep Story of Deploying IaC to Thousands of Accounts
    • 3.Custom Resource·Hooks·Change Set: CloudFormation's Extension and Validation Mechanisms
    • 4.CDK·CDK Pipelines·Terraform: Deep Comparison of Modern IaC Tools and Self-Evolving Pipelines
    • 5.Week 8 Integrated Scenario: IaC Tools Meeting Within One Incident
  • Week 9
    • 1.Systems Manager: Run Command·Session Manager·Patch Manager's Deep Story
    • 2.State Manager·Inventory·Compliance: The Abstraction of Desired State
    • 3.AppConfig: Feature Flags and Progressive Deployment
    • 4.Secrets Manager and Parameter Store: Lifecycle and Rotation
    • 5.Week 9 Integrated Scenario: Configuration Management Across Fleet Scale
  • Week 10
    • 1.CloudWatch Metrics: Time Series, Dimensions, and Alarm Evaluation Model Deep Dive
    • 2.CloudWatch Logs: Groups, Streams, Subscriptions, and Insights Deep Dive
    • 3.Container Insights·Lambda Insights·EMF: Workload-Specific Observability Deep Dive
    • 4.Synthetics·RUM·Evidently: Three Lenses Measuring User Experience
    • 5.Week 10 Synthesis: Tying Observability into Incidents
  • Week 11
    • 1.X-Ray: Causal Graphs of Distributed Tracing and the Deep Story of the Trace Model
    • 2.X-Ray Sampling: Reservoir Algorithm and the Economics of Tracing at Operational Scale
    • 3.ADOT: The Deep Story of OpenTelemetry Ending the Tracing Tool Wars
    • 4.OpenSearch · AMP · AMG: The Two Worlds of Inverted Indices and Time-Series Databases
    • 5.Week 11 Synthesis: Real-World Decision-Making in Tracing and Telemetry Observability
  • Week 12
    • 1.EventBridge: Event Bus Routing Model and the Nervous System of Asynchronous Automation
    • 2.Systems Manager Automation: Codifying Runbooks and the Operator's Disappearance
    • 3.Auto-Healing and Control Theory: When Systems Repair Themselves
    • 4.ChatOps and Incident Manager: The Coordination Layer
    • 5.Week 12 Synthesis: The Five-Stage Pipeline and Decision Trees
  • Week 13
    • 1.Multi-AZ High Availability: Distributed Principles Underlying Replication Consistency, Quorum, and Failover
  • Week 14
    • 1.GuardDuty and Automatic Isolation: Signal Processing, Statistics, and Auto-Response Principles
    • 2.Security Hub: SIEM Principles of Normalization, Aggregation, and Auto-Remediation
    • 3.AWS Config: Closed-Loop Control Principles for State Recording, Drift Detection, and Automated Remediation
    • 4.Audit Manager, Macie, Inspector: Evidence Automation, Data Classification, Vulnerability Scanning Principles
    • 5.Week 14 Comprehensive Review: The Big Picture of Security Automation Stack and Practical Scenarios
  • Week 15
    • 1.Multi-Account Enterprise CI/CD: Governance and Platform Engineering Principles for 50+ Accounts
    • 2.Hybrid CI/CD: Bridging On-Premises and AWS into One Deployment Model
    • 3.Large-Scale ECS/EKS Operations: Scheduling, GitOps, Cost Principles for 100+ Microservices
    • 4.Serverless Large-Scale Incident Auto-Response: Recovery Without People, Safety Rails
    • 5.Week 15 Synthesis: Reading Signals and Trade-Off Judgment
  • Week 16
    • 1.Domain 1+2 Integrated Review: SDLC Automation and IaC as One Thread
    • 2.Domain 3+4 Integrated: Resilience and Observability as Failure Prevention
    • 3.Incident Response and Security Compliance Woven Through Everything
    • 4.Full Exam Scenarios (Domains 1-6 Integrated)
    • 5.D-Day Exam Prep: Mental State, Time Management, Last-Minute Do's and Don'ts
SCS-C03 · SpecialtySecurity - Specialty
MLA-C01 · AssociateMachine Learning Engineer - Associate
AIF-C01 · FoundationalAI Practitioner - Foundational
DEA-C01 · AssociateData Engineer - Associate
MLS-C01 · SpecialtyMachine Learning - Specialty
← DOP-C02/Week 16/Day 3
DOP-C02· ProWeek 16 · Day 3~13 min read

Day 3 - Incident Response and Security Compliance Woven Through Everything

Today: incident response (8%) and security (14%), together 22% of the exam. Unlike Domains 1-4, these don't cluster as separate topics but rather are cross-cutting. Every pipeline has security gates. Every incident should have audit trail. Today: treat these as properties of all systems, not silos.

Incident Response Fundamentals — MTTR, Root Cause, Runbook Automation

Incident response has one north star: Mean Time To Recover (MTTR). From detection to system restored.

MTTR = Detection Time + Diagnosis Time + Remediation Time + Validation Time

💡 Related theory: Each component is attackable. Reduce detection time: lower alarm threshold, add synthetic checks

여기부터는 Pro 전용입니다

Week 1은 누구나 무료로 볼 수 있어요. Week 2부터의 전체 학습 자료와 모의고사·무제한 복습은 Pro 플랜에서 이용할 수 있습니다.

Pro 알아보기로그인
PreviousDomain 3+4 Integrated: Resilience and Observability as Failure PreventionWeek 16 · Day 2Next Full Exam Scenarios (Domains 1-6 Integrated)Week 16 · Day 4