Choosing the Right AWS Database: Aurora, DocumentDB, Keyspaces, Neptune, Timestream, OpenSearch and Redshift for Developers

AWS Developer Associate 40 min min read Updated: Nov 17, 2026 Intermediate
Choosing the Right AWS Database: Aurora, DocumentDB, Keyspaces, Neptune, Timestream, OpenSearch and Redshift for Developers
Intermediate Topic 3 of 3

Purpose-Built Databases

AWS offers many databases because one engine does not fit every access pattern. Pick by data shape and how you read it, not by habit.

TypeServiceTypical use
Relational (OLTP)RDS, AuroraOrders, accounts, ERP, SQL joins, strict schema
Key-value / documentDynamoDBShopping carts, sessions, IoT state, high scale APIs
In-memoryElastiCache, MemoryDBCaching, leaderboards, real-time counters
Document (MongoDB-compatible)DocumentDBContent catalogs, user profiles, MongoDB apps
Wide-column (Cassandra-compatible)KeyspacesServerless Cassandra for time-ordered and high-write workloads
GraphNeptuneSocial graphs, fraud rings, recommendations, knowledge graphs
Time seriesTimestreamIoT and application metrics over time
Search and analytics on logsOpenSearch ServiceFull-text search, log analytics, dashboards
LedgerAmazon QLDB (check current status) or Aurora/DynamoDB with audit designImmutable, verifiable history
Data warehouse (OLAP)RedshiftComplex analytical SQL over huge data
Lake queriesAthena on S3Ad-hoc SQL on files
Services evolve AWS adds and retires services over time. Before choosing a niche service for a new project, check its current availability and status in the AWS documentation.

Amazon DocumentDB

  • MongoDB-compatible managed document database with a Aurora-like storage layer (6 copies across 3 AZs, up to 15 replicas)
  • Use the MongoDB drivers with a few differences. Not every MongoDB feature is supported
  • Choose it to lift MongoDB apps with little change. Choose DynamoDB for serverless key access at huge scale
python from pymongo import MongoClient c = MongoClient("mongodb://app:secret@docdb.cluster-abc.ap-south-1.docdb.amazonaws.com:27017/?tls=true&replicaSet=rs0&readPreference=secondaryPreferred&retryWrites=false", tlsCAFile="global-bundle.pem") c.shop.products.insert_one({"sku": "P-7", "name": "Lamp", "tags": ["home", "light"]}) print(c.shop.products.find_one({"sku": "P-7"}))

Amazon Keyspaces

  • Serverless, Apache Cassandra-compatible (CQL). Scales automatically, no clusters
  • Use when you already use Cassandra or need wide-column modeling and CQL drivers

Amazon Neptune

A graph database for highly connected data. It supports Gremlin and openCypher (property graphs) and SPARQL (RDF). Relationship queries that need many joins in SQL become simple traversals.

text // Gremlin: people who bought what my friends bought g.V().has('person','name','Asha').out('friend').out('bought').dedup().values('title')
  • Use for fraud detection, recommendations, social networks, network topology, identity graphs
  • Neptune Analytics supports graph analytics and vector search for GenAI use

Amazon Timestream

  • Serverless time series database with automatic tiering between memory and magnetic storage and built-in time functions
  • Use for IoT sensor data, DevOps metrics, clickstream over time
  • Query with SQL (ago(1h), bin(time, 5m)). Check the current availability and recommended engine options (Timestream for LiveAnalytics and for InfluxDB) before choosing
sql SELECT bin(time, 5m) AS t, avg(measure_value::double) AS avg_temp FROM "iot"."sensors" WHERE device = 'dev-7' AND time > ago(1h) GROUP BY bin(time, 5m) ORDER BY t

Amazon OpenSearch Service

  • Managed OpenSearch (and legacy Elasticsearch) clusters or serverless collections
  • Use for full-text search, autocomplete, log and security analytics, vector search for AI, dashboards
  • Not a primary database. Keep the source of truth in DynamoDB, RDS or S3 and index a copy, for example with DynamoDB Streams to OpenSearch or Firehose
  • Common pattern: Kinesis Firehose to OpenSearch for logs

Amazon Redshift

  • Columnar, massively parallel data warehouse for analytics over terabytes to petabytes
  • Serverless or provisioned. Redshift Spectrum queries S3 data. Zero-ETL integrations load from Aurora and DynamoDB
  • Not for high-rate single-row OLTP. Use it for dashboards and reports

Decision Guide

QuestionAnswer
Need joins, foreign keys, ACID SQL?Aurora / RDS
Known key lookups, serverless, scale without limit?DynamoDB
Sub-millisecond reads of hot data?ElastiCache / DAX
Existing MongoDB app?DocumentDB
Existing Cassandra app?Keyspaces
Queries follow relationships (friends of friends)?Neptune
Data points with timestamps, trends and downsampling?Timestream
Search box, relevance ranking, log search?OpenSearch
BI over huge historical data?Redshift or Athena + S3
Ad-hoc SQL on files, pay per query?Athena

Polyglot Persistence Example

text Online shop Orders and payments → Aurora (ACID transactions) Cart and sessions → DynamoDB / ElastiCache Product search → OpenSearch (fed by DynamoDB Streams) Recommendations → Neptune Clickstream events → Kinesis Firehose → S3 → Athena / Redshift

Practice Tasks

  1. Pick a database for five scenarios and defend the choice in one sentence each
  2. Index a DynamoDB table into OpenSearch with a Stream-triggered Lambda
  3. Run a Gremlin or openCypher query on a small Neptune graph
  4. Store sensor readings in a time series database and query hourly averages
  5. Query a CSV in S3 with Athena

Conclusion

Choose the database by data shape and access pattern: Aurora or RDS for relational, DynamoDB for key access at scale, ElastiCache for speed, DocumentDB for MongoDB, Keyspaces for Cassandra, Neptune for graphs, Timestream for time series, OpenSearch for search and Redshift or Athena for analytics. Combine several when needed and check service status before adopting niche ones.

Quick Summary: purpose-built map; DocumentDB; Keyspaces; Neptune; Timestream; OpenSearch; Redshift; decision guide; polyglot example.

Get Newsletter

Subscibe to our newsletter and we will notify you about the newest updates on Edugators