Skip to Content
Cloud Engineering Academy
6. Databases & Data Architecture

Module 6 cheat sheet

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

SAA-C03DEA-C01DVA-C03

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

A printable summary of Module 6. Each row links back to the lesson with the detail.

Key services

ServiceWhat it is for
RDS for SQL Server / PostgreSQLManaged relational engine; you own network, identity, keys, parameters and schema
Aurora (PostgreSQL, MySQL)Shared cluster volume, up to 15 readers, Serverless v2, Global Database
Babelfish for Aurora PostgreSQLT-SQL and TDS compatibility layer; subset only, assess first
DynamoDBKey-value at scale for known access patterns: idempotency records, lookups, audit
ElastiCache (Valkey / Redis OSS)Sub-millisecond cache, counters, sessions; never a system of record by default
DocumentDBMongoDB-compatible (not MongoDB) documents: catalogues, flexible forms
Redshift / S3 + AthenaWarehouse and lake for history and analytics, off the OLTP database
RDS ProxyConnection multiplexing, faster failover handling; paid per vCPU-hour
DMS + DMS Schema ConversionFull load + CDC, and T-SQL to PostgreSQL conversion with assessment
KMS / Secrets ManagerCustomer managed key at rest; rotated credentials
CloudWatch Database InsightsDB load by wait event and top SQL (replaced the Performance Insights console)

.NET / Azure → AWS

Microsoft / AzureAWS
SQL Server / Azure SQL MIRDS for SQL Server
Azure SQL Database serverlessAurora PostgreSQL Serverless v2
Always On AG (sync secondary)Multi-AZ DB instance (standby not readable)
Always On readable secondariesMulti-AZ DB cluster or read replicas
sp_configure, SQL Agent optionsParameter groups and option groups
Cosmos DBDynamoDB
Azure Cache for RedisElastiCache for Valkey
Synapse dedicated poolRedshift / Redshift Serverless
Managed identity to Azure SQLIAM database authentication (not SQL Server)
Key Vault TDE keyKMS customer managed key, chosen at creation
DMA / SSMADMS Schema Conversion + DMS
Query Store / Query Performance InsightDatabase Insights + pg_stat_statements / Query Store

Most useful CLI commands

TaskCommand
Engine versions availableaws rds describe-db-engine-versions --engine postgres
Instance status and settingsaws rds describe-db-instances --db-instance-identifier ID
Wait until readyaws rds wait db-instance-available --db-instance-identifier ID
Manual snapshotaws rds create-db-snapshot --db-instance-identifier ID --db-snapshot-identifier SNAP
Point-in-time restore (new instance)aws rds restore-db-instance-to-point-in-time ...
Restore from snapshotaws rds restore-db-instance-from-db-snapshot ...
Aurora cluster restoreaws rds restore-db-cluster-to-point-in-time ...
Inspect proxiesaws rds describe-db-proxies
Create DynamoDB tableaws dynamodb create-table ...
Query DynamoDBaws dynamodb query --table-name T --key-condition-expression ...
Enable TTLaws dynamodb update-time-to-live --table-name T --time-to-live-specification ...
Check a secretaws secretsmanager describe-secret --secret-id ID
Clean upaws rds delete-db-instance --db-instance-identifier ID --skip-final-snapshot (lab only), then delete snapshots and parameter groups

Key limits and defaults

ItemValueLesson
Automated backup retention0 to 35 days; 0 disables PITR; console default 7, CLI default 1Multi-AZ, replicas, backups, PITR
PITRAny second in the window, typically within about 5 minutes of now, always to a new instanceMulti-AZ, replicas, backups, PITR
Manual snapshot quota100 per RegionMulti-AZ, replicas, backups, PITR
Multi-AZ instance failoverTypically 60 to 120 secondsMulti-AZ, replicas, backups, PITR
RDS read replicasUp to 15 per primary; SQL Server Enterprise onlyMulti-AZ, replicas, backups, PITR
Aurora storage and readersSix copies across three AZs; writer plus up to 15 readersAmazon Aurora
Aurora Global DatabaseOne writer Region, up to 10 secondaries, typically under 1 s lagAmazon Aurora
gp3 baseline3,000 IOPS and 125 MiB/s (PostgreSQL rises to 12,000 and 500 at 400 GiB)RDS
IAM database auth tokenValid 15 minutes; PostgreSQL, MySQL, MariaDB onlyEncryption and database access
RDS Proxy timeoutsIdle client 1,800 s; maximum connection life 24 hConnection pooling and RDS Proxy
DynamoDB item size400 KB including attribute namesDynamoDB fundamentals
DynamoDB Query/Scan pageUp to 1 MB per call; paginate with LastEvaluatedKeyDynamoDB fundamentals
TransactWriteItemsUp to 100 actions, 4 MB, one Region, each item once, double capacity costDynamoDB for banking correctness
DynamoDB Streams retention24 hoursDynamoDB for banking correctness
PostgreSQL error codes40001 serialization failure: retry the whole transaction; 25006 read-only (failover)Transactions · EF Core on AWS

Decision rules

If…Then…
Joins, integrity, ACID ledgerRelational: RDS or Aurora PostgreSQL
T-SQL heavy, licences fixedRDS for SQL Server (licence cost drives the decision)
T-SQL heavy in-house app, wants lower licence costAssess Babelfish, then test; do not assume
Known key lookups, idempotency, huge scaleDynamoDB with on-demand capacity
Hot reads, rate limits, sessionsElastiCache for Valkey with HybridCache; fail-open or fail-closed decided per use
Flexible JSON, no moneyDocumentDB, or jsonb on an existing Aurora cluster
Years of history, ad hoc analysisS3 + Athena; Redshift for high-concurrency complex SQL
Lambda or bursty autoscaling exhausts connectionsBudget connections, shrink pools, then add RDS Proxy
No password wanted (PostgreSQL, MySQL, MariaDB)IAM database authentication; otherwise Secrets Manager with alternating-users rotation
Lost updatesGuarded atomic UPDATE ... WHERE balance >= @amount, or a concurrency token
Duplicate payment riskUnique key plus stored response, claimed in the same transaction as the money movement
Migrations in CI/CDBundle or script, one-shot job, direct connection (not the proxy)
Migration cut-overDMS full load + CDC, independent validation, agreed rollback

Common exam traps

  • Multi-AZ is not a backup. A bad delete replicates; use PITR or snapshots.
  • The Multi-AZ instance standby does not serve reads; read replicas and Aurora readers do.
  • Replicas are asynchronous: a read just after a write may be stale.
  • Encryption at rest is chosen at creation. Encrypt an unencrypted instance by restoring a snapshot copy made with a key.
  • Snapshots under the aws/rds managed key cannot be shared; use a customer managed key.
  • IAM database authentication does not exist for RDS for SQL Server.
  • Strongly consistent DynamoDB reads are never available on a GSI; GSIs are eventually consistent.
  • TTL deletes eventually, not on time: filter expired items on read.
  • A global table or transaction is not a cross-Region transaction: transactions stay in one Region.
  • PITR restores to a new instance, never over the existing one.
  • Disabling the KMS key stops the database.
  • DocumentDB is MongoDB-compatible, not MongoDB.
  • Performance Insights console is replaced by CloudWatch Database Insights; the PI API continues.

Cost traps

TrapAvoid it by
RDS for SQL Server licence-includedDesign-only; use Developer edition in Docker
RDS, Aurora and proxies left runningDeploy and destroy the same day; stop is temporary
Manual snapshots and old restored instancesDelete after drills; they bill for storage
RDS Proxy billed per vCPU-hour of the targetAdd it only where connection exhaustion is measured
Aurora Global Database, DocumentDB, RedshiftDesign-only exercise with diagrams and an ADR
DMS replication instance running after rehearsalStop and delete tasks, endpoints and the instance
DynamoDB storage growth and scansTTL, archive to S3, query by key
Athena scanning raw CSVParquet, partitions, workgroup limits
ElastiCache idle clusterLocal Valkey in Docker for learning
Secrets Manager secrets forgottenDelete with the lab; use Parameter Store for throwaway labs

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