Capstone projects
The seven portfolio-quality capstone projects: what each builds, which modules it uses, the tested lab code it wraps, how much it costs and what you leave with. Each ends in a repository you can show an interviewer.
Assumes: .NET 10 LTS ยท AWS SDK for .NET v4 ยท Terraform AWS provider 6.x ยท Region us-east-1. Verified against official sources on 2026-11-18.
A capstone is an end-to-end, portfolio-quality system that spans several modules. It has source code, infrastructure as code, diagrams, security controls, tests, monitoring, a cost estimate, a teardown and decision records. You finish with a repository that shows how you think, not just what you built.
How the capstones are built
The capstones are project wrappers around the labs you already ran. The labs under labs/ are tested, build without an AWS account and contain the code. Each capstone, under projects/<slug>/ in the repository, adds what a lab does not: the infrastructure to join the pieces, glue code and tests where the labs meet, and the documents a reviewer expects.
Each capstone's folder holds a README.md, docs/architecture.md (big picture, data flow and security boundaries as Mermaid diagrams), docs/adr/ (short decision records), docs/security-controls.md, docs/testing.md, docs/monitoring.md, docs/cost-and-teardown.md and checklist.md (the "portfolio ready" list). The site pages in this section summarise each project and link to the lessons it relies on.
Educational projects: not compliance advice
All data is fictional (the bank is Harbourline Bank). Nothing in a capstone makes a system compliant with PCI DSS, UK GDPR or any regulation, and nothing replaces legal, security, data-protection and audit review. Every page says what is built, what is only designed and what is missing.
The seven projects
| # | Project | Planned slug | Builds on | Main services | Cost | Status |
|---|---|---|---|---|---|---|
| 1 | Secure digital banking REST API | p1-secure-banking-api | Modules 3, 4, 5, 6, 11 | ECS Fargate, API Gateway, Cognito, WAF, KMS, Secrets Manager, Aurora, CloudWatch | ๐ก about USD 0.12 to 0.20 per hour deployed | Available |
| 2 | Event-driven transaction processing | p2-event-driven-transactions | Modules 8, 14 | Step Functions, SQS, SNS, EventBridge, Lambda, DynamoDB | ๐ข free offline, cents deployed | Available |
| 3 | Banking data engineering pipeline | p3-data-engineering-pipeline | Modules 4, 7, 14 | S3, Glue, Athena, Lake Formation, Transfer Family (SFTP), Step Functions | ๐ก Transfer Family is about USD 0.30 per hour while it exists | Available |
| 4 | Complete .NET CI/CD | p4-complete-cicd | Modules 3, 9 | GitHub Actions with OIDC, ECR, ECS blue/green, CloudWatch | ๐ก about USD 0.15 to 0.20 per hour for two environments | Available |
| 5 | Highly available banking application | p5-ha-banking-app | Modules 2, 6, 11, 12 | VPC, ALB, Auto Scaling, RDS Multi-AZ, ElastiCache, AWS Backup, multi-Region DR | ๐ก about USD 0.20 per hour deployed (NAT gateway, ALB, Multi-AZ database) | Available |
| 6 | Legacy .NET Framework migration | p6-legacy-dotnet-migration | Modules 13, 6, 3 | Assessment, containerisation, DMS, RDS PostgreSQL, weighted-DNS cut-over, rollback | ๐ก about USD 0.20 to 0.25 per hour for a rehearsal (a DMS instance bills hourly while it exists) | Available |
| 7 | Secure multi-account landing zone (lite) | p7-landing-zone-lite | Modules 5, 10, 15 | Organizations, SCPs, centralised CloudTrail and Config, GuardDuty, Security Hub, IAM Identity Center, budgets | ๐ก cents to about USD 1 for a same-day rehearsal; about USD 10 to 40 a month if left running | Available |
The cost column is a list-price estimate dated 2026-11-18, not re-fetched from the pricing pages โ VERIFY. Capstone 7 is the only one that changes your AWS Organization: use a sandbox organisation.
Which capstone should I do first?
| If you want to... | Start with |
|---|---|
| Show security judgement to an employer | 1 (and add 4 for the pipeline that ships it) |
| Show you can build reliable money movement | 2 |
| Show data engineering with banking controls | 3 |
| Show delivery maturity, audit evidence and rollback | 4 |
| Show reliability: surviving a failed task, a lost Availability Zone and a lost Region, with measured RTO and RPO | 5 |
| Show you can move a legacy .NET Framework and SQL Server estate safely, with a gate and a rehearsed rollback | 6 |
| Show multi-account governance: guardrails, central logging, central detection and access by group | 7 |
Projects 1 and 4 combine well: run Capstone 1's API through Capstone 4's pipeline. Projects 2 and 3 share ideas (idempotency, quarantine, evidence). Capstone 5 gives Capstone 6 its VPC and database posture, and Capstone 7 is the foundation you would put them in.
What every capstone page contains
- What you are building, with the architecture diagram.
- The lessons and labs it builds on, as links.
- What is in the repository, split into the lab code that is referenced and the capstone additions.
- A build path, and what was verified when the page was written (tests run and their results, infrastructure validated) next to what was not run.
- Security controls with their evidence, and the honest gaps.
- Cost and teardown (every capstone ends in a teardown and a check that nothing is left).
- Acceptance criteria and a portfolio-ready checklist.
- Exercises in three tiers (๐ข guided, ๐ก challenge, ๐ด live problem), interview questions and key takeaways.
Working with the repository docs
The capstone folders are in the repository, next to the labs. They are plain Markdown so they work on GitHub, in your editor and as the start of your own portfolio repository: copy the folder, keep the structure, change the names, and replace every sentence you cannot defend with one you can.
Before you deploy anything
- Set an AWS Budget with an e-mail alert (see the cost-guardrails lesson in Module 0).
- Use the sandbox account and the
learn-sandboxSSO profile, never long-lived keys. - Tag everything
Project=cea-labso the teardown check can find it. - Read the teardown section first. Per-hour services such as Transfer Family, NAT gateways and load balancers are the usual surprises.
Back to the curriculum overview.
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 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.
Capstone 1: Secure digital banking REST API
A staff-facing banking API on ECS Fargate behind API Gateway, WAF and Cognito, with field-level KMS encryption, a blind index, audited role-based access, segregated payment signing and an Aurora data tier, built on the tested Module 3, 4 and 5 labs and finished as a portfolio repository.