All guides
Practice now
D3 · Cloud technology and services

Databases: RDS, DynamoDB, and more

AWS offers a full portfolio of managed databases for different access patterns. The CLF-C02 especially tests RDS Multi-AZ vs Read Replicas, and RDS vs DynamoDB as a choice scenario.

Databases on AWS

RDS / Aurora

Relational SQL

DynamoDB

NoSQL key-value

ElastiCache

In-memory / Cache

Redshift

Data Warehouse

Amazon RDS — Relational Database Service

Icon-Architecture/48/Arch_Amazon-RDS_48

Managed relational databases on AWS

makes it easy to set up, operate, and scale relational databases in the cloud. AWS manages the server, the operating system, engine patching, and automated backups.

Supported engines: MySQL, PostgreSQL, Oracle, Microsoft SQL Server, MariaDB, Amazon Aurora

What AWS manages in RDS

  • • Physical hardware of the database servers
  • • Operating system (no SSH access to the server)
  • • Database engine patches (MySQL, PostgreSQL, etc.)
  • • Automated backups with 0-35 days of retention
  • • Point-in-Time Recovery (PITR)
  • • Monitoring with CloudWatch
  • • Hardware firmware updates

What the customer manages in RDS

  • • Database data and schema
  • • Database users and passwords
  • • Security Groups (who can connect)
  • • Encryption at rest (enable the option on creation)
  • • Encryption in transit (SSL/TLS)
  • • Choice of instance type
  • • Storage size

RDS Multi-AZ vs Read Replicas — The most important distinction on the exam

✓ Multi-AZ —

RDS creates a synchronous replica in another Availability Zone. If the primary instance fails, RDS automatically fails over to the secondary in 1-2 minutes.

  • ✓ Automatic high availability
  • ✓ Automatic failover if an AZ fails
  • ✓ Synchronous replica (no data loss)
  • ✗ Does NOT improve read performance
  • ✗ The secondary replica does not serve normal traffic

Question: "Do I want the DB to keep running if an AZ fails?" → Multi-AZ

✓ Read Replicas — Read Scaling

RDS creates asynchronous read-only replicas. Applications can direct read queries to the Read Replicas, reducing the load on the primary instance.

  • ✓ Improves read performance
  • ✓ Up to 5 Read Replicas per RDS instance
  • ✓ Can be located in different regions
  • ✗ NOT for automatic high availability
  • ✗ Asynchronous replication (possible minor lag)

Question: "My app reads a lot of data and I need to scale?" → Read Replicas

Related labD2 · Security and Compliance

Find the bug: RDS database exposed to the internet

An external pentest found that the production database accepts direct connections from the internet. Find and fix the Security Group — no guided steps.

Diagnose a misconfigured RDS Security Group
Understand that a database SG's source should be ANOTHER Security Group, not an open IP range

+1 more...

5 min2 steps

Amazon Aurora

Icon-Architecture/48/Arch_Amazon-Aurora_48

AWS's own relational database engine, compatible with MySQL and PostgreSQL

Amazon Aurora is a relational database built by AWS from the ground up for the cloud. It's compatible with MySQL and PostgreSQL but delivers significantly higher performance.

5x

Faster than MySQL

3x

Faster than PostgreSQL

up to 15

Read Replicas per cluster

10GB → 128TB

Storage auto-scaling

Aurora vs standard RDS

  • • Aurora: AWS hardware optimized for databases. RDS: generic hardware.
  • • Aurora: storage distributed across 6 copies (3 AZs). RDS: 2 copies in Multi-AZ.
  • • Aurora: up to 15 Read Replicas. RDS: up to 5.
  • • Aurora: ~20% more expensive than equivalent RDS MySQL/PostgreSQL.

Aurora Serverless

Automatically scales database capacity based on demand. Ideal for apps with unpredictable or intermittent load. You pay only for resources used during active usage.

Amazon DynamoDB — Serverless NoSQL

Icon-Architecture/48/Arch_Amazon-DynamoDB_48

A fully managed, serverless key-value and document database

is a key-value and document database that delivers single-digit millisecond performance at any scale. It's serverless — there are no servers to manage, provision, or patch.

DynamoDB characteristics

  • •
    Serverless: no server management. Scales automatically to any size.
  • •
    Performance: consistent single-digit millisecond latency.
  • •
    Data model: tables of items (documents). No fixed schema. Only a Primary Key is required.
  • •
    Global Tables: fully managed multi-region replication.
  • •
    Streams: captures table changes so they can be processed with Lambda.

DynamoDB Accelerator (DAX)

A fully managed, in-memory cache compatible with DynamoDB. Improves performance by up to 10x for read-heavy workloads.

  • • Microsecond latency vs DynamoDB's milliseconds
  • • Compatible with existing DynamoDB APIs
  • • No application code changes required
  • • Ideal for: gaming, finance, real-time applications
Related labD3 · Cloud Technology and Services

Create a NoSQL table with Amazon DynamoDB

Create a DynamoDB table in on-demand mode and understand the key-value data model.

Differentiate DynamoDB's NoSQL model from RDS's relational model
Create a table with a partition key

+1 more...

7 min6 steps

Amazon ElastiCache

Icon-Architecture/48/Arch_Amazon-ElastiCache_48

Managed in-memory caching (Redis and Memcached)

ElastiCache is a fully managed in-memory caching service. It improves database performance by caching frequently queried data.

Redis

  • • Advanced data structures (sets, lists, hashes)
  • • Optional data persistence
  • • High availability (automatic replication)
  • • Pub/Sub messaging
  • • Recommended for most use cases

Memcached

  • • Simple key-value cache
  • • Multi-node
  • • No data persistence
  • • No replication
  • • For pure caching without advanced features

Amazon Redshift — Data Warehouse

Icon-Architecture/48/Arch_Amazon-Redshift_48

A data warehouse for petabyte-scale data analytics

Amazon Redshift is a fully managed, scalable, high-performance data warehouse. Designed for analyzing large volumes of data (OLAP), not for real-time transactions (OLTP).

Use cases (OLAP)

  • • Business Intelligence and reporting
  • • User clickstream analysis
  • • Historical sales analysis
  • • Paired with Quick Sight (formerly QuickSight) for dashboards

Not meant for (OLTP)

  • • Real-time transactions
  • • Write-heavy web applications
  • • Frequently updated data
  • • Use RDS or DynamoDB for this instead

Other database services

Icon-Architecture/48/Arch_Amazon-DocumentDB_48

Amazon DocumentDB

Document DB (MongoDB compatible)

A fully managed JSON document database, compatible with MongoDB workloads. Scales storage automatically.

When: Migrating from MongoDB, content apps, product catalogs

Icon-Architecture/48/Arch_Amazon-Neptune_48

Amazon Neptune

Graph Database

A managed graph database. Optimized for storing and querying highly connected relationships between data.

When: Social networks, recommendation engines, fraud detection, knowledge graphs

Icon-Architecture/48/Arch_Amazon-RDS_48

Amazon QLDB

Ledger Database (blockchain-like)

An immutable, cryptographically verifiable ledger database. It reached end of support on July 31, 2025; AWS recommends migrating to Aurora PostgreSQL.

When: Financial systems, transaction logging, supply chain tracking

Relational vs NoSQL — When to use each

CriterionRDS / Aurora (SQL)DynamoDB (NoSQL)
Data modelTables with relationships (JOIN)Key-value or JSON documents
SchemaRigid (schema-on-write)Flexible (schema-on-read)
ScalingVertical (more CPU/RAM) or Read ReplicasAutomatic, unlimited horizontal scaling
ACID transactionsYes, nativeYes (DynamoDB transactions, limited)
Complex queriesFull SQL: JOINs, GROUP BY, subqueriesOnly by partition key / sort key. No native JOINs.
Performance under loadDegrades with many JOINs and high concurrencyConsistent performance at any scale
Use casesERP, CRM, finance, transactional e-commerceGaming, IoT, user profiles, sessions, real time

Database migration tools

Icon-Architecture/48/Arch_AWS-Database-Migration-Service_48

Migrates data with minimal downtime

Migrates databases to AWS (or between AWS services) while the source system stays operational during the migration. Supports both continuous and one-time migrations.

Homogeneous migration

Same engine: on-prem MySQL → RDS MySQL. Just DMS, no schema conversion.

Heterogeneous migration

Different engines: Oracle → Aurora PostgreSQL. Requires SCT for the schema + DMS for the data.

AWS Schema Conversion Tool (SCT)

Automatically converts the database schema (tables, views, indexes, stored procedures) from one engine to another.

  • • Oracle → PostgreSQL / Aurora
  • • SQL Server → MySQL / Aurora
  • • Teradata → Amazon Redshift
  • • Also converts application code (JDBC, ODBC)

SCT + DMS together

SCT converts the SCHEMA (structure). DMS migrates the DATA (content). Used together for heterogeneous migrations.

Common use cases

On-premises Oracle → Amazon Aurora PostgreSQL

Tools: SCT (schema) + DMS (data)

Heterogeneous

On-premises SQL Server → Amazon RDS for SQL Server

Tools: DMS only

Homogeneous

On-premises MySQL → Amazon RDS for MySQL

Tools: DMS only

Homogeneous (DB lift-and-shift)

Teradata data warehouse → Amazon Redshift

Tools: SCT (schema) + DMS (data)

Heterogeneous
Related labD3 · Cloud Technology and Services

Create a database with RDS

Deploy a managed relational database with Amazon RDS.

Understand the managed database model
Create a MySQL RDS instance

+1 more...

15 min6 steps

Did you get this topic?

Test what you just learned

A company has an RDS MySQL database with performance problems during peak hours. Most of the traffic is read queries. Which Amazon RDS solution improves read performance without affecting the availability of the production database?

Ready to test "Databases: RDS, DynamoDB, and more"?

Put what you learned to the test with original CLF-C02 exam questions.

Start CLF-C02 mock exam

Unlimited mock exams with the Pro plan

Log in to track your progress.