Skip to Content
Cloud Engineering Academy
17. Daily-Work Playbooks & Career

Module 17 cheat sheet

One-page incident-triage and interview revision summary for Daily-Work Playbooks and Career: first questions, evidence sources, Azure mapping, CLI commands, limits, decision rules, exam traps and cost traps.

CLF-C02SAA-C03DVA-C03SCS-C03DEA-C01SOA-C03DOP-C02SAP-C03

Assumes: AWS CLI v2 · AWS SDK for .NET v4 · .NET 10 LTS · Region us-east-1 · facts as stated in the Module 17 lessons; items marked VERIFY there are not repeated as certain here. Verified against official sources on 2026-11-18.

A printable summary of Module 17. Each row links back to the playbook with the detail. For an incident, follow your bank's own process first; this page is a memory aid, not a procedure.

The method (every playbook)

Symptom, then first five minutes (scope, impact, contain), then evidence (logs, metrics, traces, CloudTrail), then ranked hypotheses, test one at a time, fix and verify, prevent recurrence, record for audit. Contain before you investigate. Never delete evidence during an incident.

Symptom to first look

SymptomFirst lookPlaybook
Customer charged twiceIdempotency key and conditional write; queue consumer dedupDuplicate payment
Batch misses its windowPer-stage timings, concurrency, data skewEOD batch overrun
Calls to a partner time outEgress path (NAT), DNS, TLS, timeouts vs retriesPartner API timeouts
AccessDeniedReal caller, then the reason phrase, then the denying layerIAM evaluation
KMS AccessDeniedExceptionKey policy first, then IAM, grants, encryption contextKMS denied
ECS tasks restartstoppedReason, exit code, task lifetimeECS restarting
Lambda timeout or slow first callDuration vs timeout, Init Duration, downstream latencyLambda timeouts
502 / 503 / 504Which hop returned it, target health, timeouts502/503/504
Browser "CORS error"Replay the preflight, read the real statusCORS
Bucket publicBlock Public Access, then CloudTrail and access logsPublic bucket
Role over-privilegedAllowed vs last-accessed; staged trimRole too broad
SQL slow after migrationPlans, statistics, parameter groups, pools, N+1Slow SQL
Messages stuck or repeatedVisibility timeout vs work time, receive count, DLQSQS
Rotation causes errorsOverlap period, cached secrets, refresh on failureKey rotation
Who read this record?Authority, subject, window; CloudTrail plus app audit logRecord access
Bill jumpedAccount, service, usage type, resource, causeBill spike

.NET / Azure to AWS

Microsoft / AzureAWS
Application Insights failuresCloudWatch Logs Insights, X-Ray / Application Signals
Activity LogCloudTrail
RBAC access deniedIAM evaluation: identity, resource, boundary, SCP/RCP, session policy; explicit deny wins
Key Vault access policiesKMS key policy + grants + IAM
App Service diagnose and solveECS events and stopped tasks, ALB target health
Cost Management alertsBudgets, Cost Anomaly Detection, Cost Explorer
Service Bus dead-letterSQS DLQ + redrive

Most useful CLI commands

TaskCommand
Who am I really?aws sts get-caller-identity --profile learn-sandbox
Decode a denial messageaws sts decode-authorization-message --encoded-message TEXT
Simulate a policyaws iam simulate-principal-policy ... (a hint, not proof)
Find a denied callaws cloudtrail lookup-events --lookup-attributes ...
Run a Logs Insights queryaws logs start-query ...
ECS stopped task detailaws ecs describe-tasks --cluster C --tasks ARN
Target healthaws elbv2 describe-target-health --target-group-arn ARN
Queue stateaws sqs get-queue-attributes --queue-url URL --attribute-names All
Redrive a DLQaws sqs start-message-move-task ... · aws sqs list-message-move-tasks ...
Contain a public bucketaws s3api put-public-access-block ...
KMS rotation statusaws kms get-key-rotation-status --key-id ID
Force a secret rotationaws secretsmanager rotate-secret --secret-id ID
Costs by serviceaws ce get-cost-and-usage ...
Leftovers after a labaws resourcegroupstaggingapi get-resources --tag-filters Key=Project,Values=cea-lab

Key limits and defaults

ItemValueLesson
ALB idle timeout60 s default, configurable502/503/504
ALB connect timeout to a target10 s502/503/504
ALB Lambda target body limit1 MB (larger response gives 502)502/503/504
Kestrel KeepAliveTimeout130 s default, so longer than the ALB's502/503/504
API Gateway REST integration timeout29 s default502/503/504
Lambda timeout3 s default, 15 min maximumLambda timeouts
SQS message retention4 days default, up to 14SQS
SQS FIFO deduplication window5 minutesSQS
CloudTrail event historyManagement events, 90 daysIAM evaluation
CloudTrail data eventsOff by default; you can only show what was loggedRecord access
KMS key deletion wait7 to 30 days, irreversible afterKey rotation
Block Public AccessFour settings, per bucket and per accountPublic bucket

Decision rules

SituationRule
Unsure it is safe to retryOnly if the server can recognise the retry (key per intent, atomic claim, replay)
Reversing a paymentApproved, idempotent, linked correcting entry; never edit
Visibility timeout vs work timeTimeout must exceed the longest handler run, or messages reappear mid-work
ECS task dies in secondsStartup crash: read the first log lines and the secrets
ECS task lives about grace plus a minuteHealth check failing: fix port, path, status or security group
Exit code 137SIGKILL: memory over limit, or slow shutdown past stopTimeout
Cross-account denialBoth the caller's policy and the resource or key policy must allow
Trimming a roleAttach the new policy before removing the old; watch a full business cycle
Rotating a database secretAlternating users, with clients that refresh on login failure
Public bucketContain with Block Public Access first; engineers give facts, the DPO decides on notification
No logs for a windowThe answer is "unknown", not "nobody"

Common exam and interview traps

TrapReality
"The simulator said allowed"It misses real-world factors; confirm with the real error and CloudTrail
"IAM allow is enough for KMS"The key policy must permit the account or the principal first
CORS "fixed" with a wildcardNot with credentials; use an exact origin list, one layer owning CORS
401 shown as CORS errorError responses need CORS headers too; authorizers must not guard OPTIONS
Raise Lambda timeout past the API limitThe API still returns 504; fix the slow path
Raising memory for an ECS loopClassify the stop first; memory is only one of six classes
CloudTrail names the personIt names the role; the application audit log must name the person
Systems Manager Incident Manager or CloudTrail LakeClosed to new customers; do not design on them

Cost-trap list

TrapWhere to look
NAT gateway data processingUsage type by bytes; add gateway or interface endpoints
Idle load balancers and forgotten instancesA step up that stays flat in the daily graph
Log ingestion and groups with no retentionCloudWatch usage types; set retention
Retry or event loopsA ramp or spike that tracks request volume
Versioning without lifecycle, old snapshotsStorage byte-hours growing
Anything left after a labTag-based sweep above; teardown within the hour

Independent learning resource — not affiliated with, endorsed or sponsored by Amazon Web Services. AWS and related marks are trademarks of Amazon.com, Inc. or its affiliates. All banking data in examples is fictional. Sample architectures are for learning and are not automatically compliant with GDPR, PCI DSS or any banking regulation.

On this page