Skip to Content
Cloud Engineering Academy
14. Advanced Banking Architecture

Module 14 cheat sheet

One-page revision summary for Advanced Banking Architecture: services, Azure mapping, CLI commands, limits, decision rules, exam traps and cost traps.

SAP-C03SAA-C03SCS-C03

Assumes: AWS CLI v2 · .NET 10 LTS · Region us-east-1 · facts as stated in the Module 14 lessons (checked 2026-11-18). Verified against official sources on 2026-11-18.

A printable summary of Module 14. Figures marked in the lessons with a verify note can change: confirm them in the current AWS documentation before you rely on them in a design.

Key services

ServiceWhat it is for in a banking design
API Gateway + CloudFront + WAF + ShieldOne controlled, protected entry per channel
Amazon CognitoCustomer sign-in, short tokens, step-up for risky actions
Step Functions StandardLong, audit-visible flows: onboarding, payments, approvals
Step Functions ExpressShort, high-volume flows (up to 5 minutes)
DynamoDBIdempotency keys, balance reservations, projections
AuroraDouble-entry ledger
Kinesis Data Streams + LambdaOrdered per-account event streams, fraud rules
EventBridge + SQSDomain events (a bus per domain) and a queue per consumer with a dead-letter queue
S3 + Glue + AthenaReports, reconciliation files, log archive queries
S3 Object LockTamper-resistant evidence in a separate log archive account
Direct Connect, Site-to-Site VPN, Amazon MQHybrid link to core banking and MQ-style messaging
AWS Backup, Aurora Global DatabaseDR building blocks, immutable cyber recovery copies

.NET / Azure → AWS

Microsoft / AzureAWS
API Management + App ServiceAPI Gateway + ECS Fargate or Lambda (VPC Link)
Service Bus + Durable FunctionsEventBridge + SQS + Step Functions
Service Bus sessions, duplicate detectionSQS FIFO groups and deduplication (5-minute window)
Azure SQL ledger tablesAurora double-entry design, DynamoDB idempotency
Stream AnalyticsKinesis Data Streams + Lambda, Managed Service for Apache Flink
Storage + Data Factory reportingS3 + Glue + Athena
Front Door + WAFCloudFront + AWS WAF + Shield
Azure Site Recovery / paired RegionsBackup, Aurora Global Database, Route 53, your own Region pairing

Most useful CLI commands

TaskCommand
Run a state machine and waitaws stepfunctions start-sync-execution --state-machine-arn <arn> --input file://in.json
List state machinesaws stepfunctions list-state-machines --profile learn-sandbox --region us-east-1
Read an idempotency itemaws dynamodb get-item --table-name hl-m14-idempotency --key file://key.json
Stream health (iterator age)aws cloudwatch get-metric-statistics --namespace AWS/Kinesis --metric-name GetRecords.IteratorAgeMilliseconds …
Query logs with SQLAthena over CloudTrail in S3 (not CloudTrail Lake)
Anything left tagged after a lab?aws resourcegroupstaggingapi get-resources --tag-filters Key=Project,Values=cea-lab
Tear down the lab stackcdk destroy from labs/m14-payment-saga-failures/infra/cdk

Key limits and defaults

ItemValueLesson
Step Functions Standard max time1 year; history kept 90 days after closeAPI orchestration
Step Functions Express max time5 minutesAPI orchestration
State input or output256 KiB; pass referencesAPI orchestration
Standard execution history25,000 eventsAPI orchestration
REST API sync timeout (default)About 29 s ⚠ VERIFYPayment processing
Kinesis per shardAbout 1 MB/s or 1,000 records/s in, 2 MB/s out ⚠ VERIFYReal-time
SQS FIFO dedup window5 minutesPayment processing
DynamoDB TTL deletionCan lag by hours; do not rely on exact expiryPayment processing

Decision rules

If…Then…
Flow outlives a request, needs approval or audit historyStep Functions Standard
Flow is short, pure and unit-testableIn-service code
Scheme or core times outOutcome is unknown: query by business reference before retry or refund
Before the scheme accepts / afterCompensate (release the hold) / move forward only (settle, later return)
Order mattersPer account: partition key or FIFO group, never global
Any consumer, any queueAssume at-least-once, make it idempotent
Model call in a fraud pathShort timeout plus a monitored fallback rule set
Audit logsSeparate account, Object Lock, validation, protected key
Choosing a DR strategyStart from impact tolerance, pick the cheapest that meets measured RTO and RPO

Common exam traps

TrapReality
Amazon Fraud Detector for new fraud designClosed to new customers (2025-11-07): rules on Kinesis and Lambda, SageMaker AI or Bedrock
CloudTrail Lake or Audit Manager for new designsClosed to new customers (2026-05-31) / no new onboarding (2026-04-30): CloudTrail to S3 with Athena, own evidence catalogue
Express workflows for long human approvalsExpress stops at 5 minutes: use Standard
Exactly-once from EventBridge or SQS standardAt-least-once, unordered: idempotent consumers
Retry after a timeoutCan double-pay: enquire first, use idempotency keys
"Compliant by using AWS"Never: design shows touchpoints, specialists sign off

Cost traps

TrapWhy
Step Functions Standard at volumeBilled per state transition
Kinesis shards left runningHourly billing: stop within the hour or simulate locally
Direct Connect, Amazon MQ, multi-Region DRRun all day, design-only in a sandbox
SageMaker endpoints for scoringAlways-on instances: design-only or a local rules engine
Verbose logging of payloadsStorage and personal-data risk
Lab stack not destroyedRun cdk destroy, then check tagged resources

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