Databases / Amazon Web Services

Amazon Web Services databases.

AWS offers managed versions of familiar database engines alongside purpose-built relational, document, key-value, graph, search, and analytical services. Start with application compatibility and the actual read/write patterns.

← All databases and providers

How to build the shortlist.

  1. RDS hosts several different engines. Compare the exact engine, version, license, and availability configuration rather than treating RDS as one database.
  2. Aurora and Aurora DSQL have different architectures and SQL boundaries. A global read replica is not the same as an independently writable region.
  3. DynamoDB key design, DocumentDB compatibility, Neptune query models, and Redshift analytical workloads each deserve a separate prototype.

Review the exact product, region, version, and service configuration before making a production decision. Sources checked September 8, 2026.

Provider’s database overview ↗

9 engines and services to compare.

Amazon Web Services · Managed service

Amazon Aurora

Relational

AWS; MySQL-compatible or PostgreSQL-compatible database

When to consider it

Evaluate Aurora for relational applications on AWS that fit one of its supported compatibility models. Compare it with RDS for the same engine, using realistic read/write patterns and recovery requirements.

What to check

Aurora is not identical to stock MySQL or PostgreSQL. Check engine features, extension support, I/O pricing, replica behavior, and regional write topology.

Official documentation ↗

Amazon Web Services · Managed service

Amazon Aurora DSQL

Relational / Distributed SQL

AWS; serverless distributed SQL with PostgreSQL compatibility

When to consider it

A candidate for distributed transactions with concurrent regional read/write endpoints and strong consistency. Consider it when the selected AWS region set and supported SQL features match a new or adaptable application.

What to check

DSQL is distinct from Aurora PostgreSQL. Validate supported SQL, transaction retries, snapshot isolation, and region sets; current multi-region clusters do not span continents.

Official documentation ↗

Amazon Web Services · Managed service

Amazon DocumentDB

Document

AWS; document database with MongoDB compatibility

When to consider it

Evaluate DocumentDB when a document workload belongs in AWS and its supported MongoDB-compatible interfaces cover the application. Include a comparison with MongoDB Atlas and a relational JSON approach.

What to check

MongoDB compatibility does not mean it runs MongoDB or supports every feature. Test operators, indexes, transactions, drivers, and migration tools against the exact DocumentDB engine version.

Official documentation ↗

Amazon Web Services · Managed service

Amazon DynamoDB

Key-value / Document

AWS; managed key-value and document database

When to consider it

Useful for predictable key-oriented access patterns where partition design and managed scaling suit the application. Design primary keys and secondary indexes from the reads the application must perform.

What to check

Hot keys, indexes, and consistency choices affect the design. Global table consistency modes and index read guarantees differ; check the exact API and configuration.

Official documentation ↗

Amazon Web Services · Managed service

Amazon ElastiCache

Cache / Key-value

AWS; managed Valkey, Redis OSS, and Memcached offerings

When to consider it

Useful for offloading repeated reads, session access, and other low-latency cache operations from a primary database. Select an engine and deployment based on actual client and data requirements.

What to check

Treat eviction, persistence, failover, and cache rebuilding as explicit choices. ElastiCache and durable database services serve different reliability needs.

Official documentation ↗

Amazon Web Services · Managed service

Amazon Neptune

Graph

AWS; managed graph database

When to consider it

Consider Neptune when graph traversals or RDF queries are central and the selected graph model and query language match the application. Fraud relationships and connected-data queries are common evaluation scenarios.

What to check

Property graphs and RDF are different modeling choices. Test supported query languages, highly connected nodes, ingestion, and the regional deployment topology.

Official documentation ↗

Amazon Web Services · Managed service

Amazon OpenSearch Service

Search

AWS; managed search and analytics service

When to consider it

A candidate for indexed search, log exploration, and retrieval workloads in AWS. It provides a managed operating path for workloads that match the supported OpenSearch features.

What to check

Choose provisioned or serverless capabilities deliberately. Index mappings, shard design, ingestion, access controls, and reindexing still require ownership.

Official documentation ↗

Amazon Web Services · Managed service

Amazon RDS

Relational

AWS; PostgreSQL, MySQL, MariaDB, SQL Server, Oracle Database, or Db2

When to consider it

A managed hosting choice when you want an established relational engine on AWS. It is especially relevant when engine compatibility and reducing routine infrastructure maintenance matter more than changing the data model.

What to check

RDS is a service, not a single database engine. Versions, licensing, extensions, administrative access, and availability options depend on the selected engine and configuration.

Official documentation ↗

Amazon Web Services · Analytics platform

Amazon Redshift

Analytics

AWS; managed data warehouse with provisioned and serverless options

When to consider it

A warehouse candidate for SQL reporting, analytical joins, and data pipelines in AWS. Evaluate it when the workload needs shared analysis rather than a primary store for application transactions.

What to check

Compare query concurrency, data layout, ingestion, and compute choices. PostgreSQL-related SQL familiarity does not make Redshift a replacement for an OLTP PostgreSQL server.

Official documentation ↗

Compare other providers.

Continue your work

Take the next step.