Module 17: Daily-Work Playbooks & Career
Step-by-step diagnosis guides for the problems you will actually face in a bank running .NET on AWS, from duplicate payments to AccessDenied errors and surprise bills. The module closes with interview preparation, whiteboard practice and a guide to presenting your capstone projects as a portfolio.
Assumes: .NET 10 LTS · AWS SDK for .NET v4 · AWS CLI v2 · Region us-east-1. Verified against official sources on 2026-11-18.
Step-by-step diagnosis guides for the problems you will actually face in a bank running .NET on AWS, from duplicate payments to AccessDenied errors and surprise bills. The module closes with interview preparation, whiteboard practice and a guide to presenting your capstone projects as a portfolio.
| Estimated time | About 14 hours (playbooks 9 h · career 5 h); playbooks can also be read on demand at any point |
| Priority for you | High — direct help for daily work |
| Level | Intermediate → advanced |
| Certifications | Cross-cutting. See the skills matrix |
| Cost profile | 🟢 mostly local reproductions · 🟡 optional deploy-and-destroy reproductions |
Why this matters in banking
Incidents in a bank are expensive and visible: a duplicated payment reaches a customer's statement, an overrunning end-of-day batch delays regulatory reporting, an AccessDenied blocks a release on change night. What separates a senior engineer is a calm, repeatable method — gather evidence, form a hypothesis, test it, fix it, and leave an audit trail. Each playbook here follows the same shape so the method becomes a habit.
Every playbook is structured as: symptom → first five minutes → evidence to collect (logs, metrics, traces, CloudTrail) → likely causes ranked → fix → prevent recurrence → what to record for audit.
From .NET/Azure to AWS
| You know (Microsoft/Azure) | AWS equivalent | What's different |
|---|---|---|
| Application Insights failures blade | CloudWatch Logs Insights, X-Ray / Application Signals traces | You query structured logs and traces directly |
| Azure Activity Log | AWS CloudTrail | Every API call, including who assumed which role |
| Azure RBAC "access denied" | IAM policy evaluation (identity, resource, SCP, RCP, boundaries, session policies) | More layers can deny; explicit deny always wins |
| Key Vault access policies | KMS key policies + grants + IAM | The key policy must allow the account before IAM counts |
| App Service diagnose and solve | ECS events, stopped-task reasons, ALB target health | Health checks decide restarts and routing |
| Azure Cost Management alerts | Budgets, Cost Anomaly Detection, Cost Explorer | Investigate by service, account, tag and usage type |
| Service Bus dead-letter queue | SQS DLQ + redrive | Visibility timeout and maxReceiveCount drive behaviour |
Learning objectives
By the end of this module you can:
- Apply a consistent diagnostic method to production problems and record evidence suitable for audit.
- Diagnose IAM and KMS authorisation failures by reading the policy evaluation chain.
- Troubleshoot ECS, Lambda, ALB and API Gateway failures from their logs, metrics and events.
- Investigate data, messaging and performance issues after a migration to AWS.
- Respond to security findings such as a public bucket or an over-broad role.
- Answer cloud engineer, .NET cloud developer and solutions architect interview questions with clear, structured stories.
- Present your capstone projects as a professional portfolio.
Prerequisites
- Module 3: .NET on AWS, Module 5: Security, Module 8: Messaging and Module 11: Monitoring for most playbooks
- Individual playbooks list their own prerequisites; read them when the situation arises
How the pieces fit
Lessons
The lessons are in teaching order. The playbooks are written to be read on demand as well: each lists its own prerequisites. Start with playbook 1, because several later ones build on its idempotency ideas, and keep the cheat sheet open during an incident.
Playbooks:
- Duplicate payment on client retry — trace the retry, check idempotency keys and conditional writes, and reverse safely.
- End-of-day batch overrunning its window — find the slow stage, check concurrency and data skew, and buy time safely.
- Partner API timeouts — egress path, DNS, TLS, timeouts vs retries, circuit breakers and the partner's rate limits.
AccessDeniedand IAM policy evaluation — read the error, find the denying layer, use CloudTrail and IAM Access Analyzer.KMS AccessDeniedException— key policy, grants, encryption context, cross-account keys and service principals.- ECS task keeps restarting — stopped reasons, health-check paths and grace periods, memory limits and missing secrets.
- Lambda timeouts and cold starts — duration vs timeout, VPC and downstream latency, init time, Native AOT and SnapStart.
- 502/503/504 from ALB or API Gateway — which hop returned it, target health, idle timeouts and integration timeouts.
- CORS failures — preflight requests, where CORS is configured (API Gateway vs app), and credentials rules.
- S3 bucket accidentally public — contain with Block Public Access, assess access via logs, notify per incident process.
- IAM role too broad — use last-accessed data and Access Analyzer policy generation to right-size safely.
- Slow SQL after migration to RDS — Performance Insights or CloudWatch Database Insights (current naming ⚠ VERIFY), plans, statistics, parameter groups, connection pools and N+1 queries.
- SQS messages stuck or redelivered — visibility timeout, consumer errors, DLQ inspection and redrive.
- Key rotation without downtime — KMS automatic rotation vs manual key swap, and secret rotation with dual credentials.
- "Who accessed this customer record?" — CloudTrail data events, application audit logs and correlation IDs; prepare evidence for the data protection team.
- Unexpected AWS bill spike — Cost Explorer by service and usage type, anomaly alerts, finding forgotten resources and preventing repeats.
Career:
- Interview preparation — cloud engineer — operations, networking, IAM and troubleshooting stories.
- Interview preparation — .NET cloud developer — SDK, hosting, messaging and secure coding on AWS.
- Interview preparation — solutions architect — requirements, trade-offs, cost and security reasoning.
- Architecture whiteboard practice — timed design exercises using the banking scenarios from Module 14.
- Portfolio guide — presenting the seven capstones: READMEs, diagrams, ADRs, cost notes and a short demo script.
Labs and module project
The four labs below are planned and coming: there are no lab pages yet. Each playbook already contains a runnable local reproduction, so you can start there.
- Lab 17.1 (🟢) — coming — Reproduce a duplicate payment locally with a retrying client, then fix it with an idempotency key.
- Lab 17.2 (🟢) — coming — IAM policy-evaluation puzzles: diagnose ten fictional
AccessDeniedmessages from policies and CloudTrail records. - Lab 17.3 (🟡 optional) — coming — Deploy a deliberately broken ECS service (wrong health-check path), diagnose it, fix it and destroy it.
- Lab 17.4 (🟢) — coming — Mock interview with the AI assistant for each of the three roles.
Module project — portfolio and incident report. Write a blameless incident report for one playbook scenario you reproduced, and publish a portfolio page covering your completed capstones (Capstones 1–7), each with architecture, security controls, cost estimate and teardown notes.
Cost profile
| Part | Label | Free alternative |
|---|---|---|
| Playbook reading and local reproductions | 🟢 free | Docker, SAM local, DynamoDB Local, AWS Emulator |
| IAM/KMS puzzles and CloudTrail analysis | 🟢 free | Provided fictional policy and log samples |
| Reproducing ECS/ALB failures in AWS | 🟡 credits | Deploy-and-destroy within an hour, or use the provided log samples |
| Interview and portfolio work | 🟢 free | No AWS resources needed |
Certification alignment
| Exam | Domains (weight) | What this module covers |
|---|---|---|
| DVA-C03 | Troubleshoot (22%) | Lambda, API Gateway, SQS and SDK troubleshooting |
| SOA-C03 | Monitoring (22%) · Reliability (22%) | Operational diagnosis and remediation |
| SCS-C03 | IR (14%) · IAM (20%) | Public bucket, broad roles, IAM/KMS denials, access audits |
| DOP-C02 | IR (14%) · Monitoring (15%) | Incident handling and prevention |
| SAA-C03 · SAP-C03 | Design reasoning | Whiteboard and architecture interview practice |
The domain labels are short forms; see each exam page and the skills matrix for the full mapping.
Service availability notes
Incident tooling — verified 2026-11-17
AWS Systems Manager Incident Manager has been closed to new customers since 2025-11-07, so these playbooks do not depend on it; follow your bank's own incident process and tooling. AWS CloudTrail Lake closed to new customers on 2026-05-31; the "who accessed this record?" playbook uses CloudTrail trails with Athena or CloudWatch Logs instead.
Key AWS services
AWS CloudTrail · Amazon CloudWatch (Logs Insights, metrics, alarms, Application Signals) · AWS X-Ray · IAM and IAM Access Analyzer · AWS KMS · AWS Secrets Manager · Amazon ECS · AWS Lambda · Elastic Load Balancing · Amazon API Gateway · Amazon S3 · Amazon SQS · Amazon DynamoDB · Amazon RDS (Performance Insights) · AWS Cost Explorer · AWS Budgets · AWS Cost Anomaly Detection · Amazon Athena
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.
Module 16 cheat sheet
One-page revision summary for Generative AI on AWS for Banking: services, Azure mapping, CLI commands, limits, decision rules, exam traps and cost traps.
Playbook: duplicate payment on client retry
Trace how one customer instruction became two payments, prove it from logs and the transactions table, reverse the duplicate safely with an auditable correcting entry, and close the gap with idempotency keys and conditional writes.