# Which AWS Database should you use?

DevFeed: [Which AWS Database should you use?](<https://devfeed.tech/articles/which-aws-database-should-you-use-141386.md>)

Original publisher: [Read original article](<https://aws.amazon.com/blogs/database/which-aws-database-should-you-use/>)

Author: Joseph Idziorek

Published: 2026-11-18T17:10:51Z

Content type: comparison

Language: en

Sources: [AWS Database Blog](<https://devfeed.tech/sources/aws-database-blog.md>)

Topics: [Amazon DynamoDB](<https://devfeed.tech/topics/amazon-dynamodb.md>), [Amazon Web Services](<https://devfeed.tech/topics/aws.md>), [self-hosted databases vs managed services](<https://devfeed.tech/topics/self-hosted-databases-vs-managed-services.md>), [Amazon ElastiCache](<https://devfeed.tech/topics/amazon-elasticache.md>), [Amazon RDS](<https://devfeed.tech/topics/amazon-rds.md>), [legacy systems](<https://devfeed.tech/topics/legacy-systems.md>), [Amazon DocumentDB](<https://devfeed.tech/topics/amazon-documentdb.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [agentic](<https://devfeed.tech/tags/agentic.md>), [agents](<https://devfeed.tech/tags/agents.md>), [amazon-com](<https://devfeed.tech/tags/amazon-com.md>), [amazon-dynamodb](<https://devfeed.tech/tags/amazon-dynamodb.md>), [amazon-elasticache](<https://devfeed.tech/tags/amazon-elasticache.md>), [amazon-neptune](<https://devfeed.tech/tags/amazon-neptune.md>), [application](<https://devfeed.tech/tags/application.md>), [architecture](<https://devfeed.tech/tags/architecture.md>), [aws](<https://devfeed.tech/tags/aws.md>), [building](<https://devfeed.tech/tags/building.md>), [customer-value](<https://devfeed.tech/tags/customer-value.md>), [database](<https://devfeed.tech/tags/database.md>), [databases](<https://devfeed.tech/tags/databases.md>), [foundational-100](<https://devfeed.tech/tags/foundational-100.md>), [job](<https://devfeed.tech/tags/job.md>), [legacy](<https://devfeed.tech/tags/legacy.md>), [legacy-application](<https://devfeed.tech/tags/legacy-application.md>), [managed](<https://devfeed.tech/tags/managed.md>), [refactoring](<https://devfeed.tech/tags/refactoring.md>), [selection](<https://devfeed.tech/tags/selection.md>), [thought-leadership](<https://devfeed.tech/tags/thought-leadership.md>)

## AI overview

The article recommends choosing an AWS database by workload: for migrations, use the managed equivalent of the existing database, starting with serverless when possible; for legacy relational refactoring, start with Aurora PostgreSQL serverless, and adopt multiple purpose-built databases only when access patterns or scaling needs warrant it. For new applications, use a database the team already knows; otherwise, start with PostgreSQL, with Aurora PostgreSQL serverless for managed PostgreSQL or Aurora DSQL for relational workloads needing scale and operational simplicity. DynamoDB is suggested for known access patterns and very high throughput, while ElastiCache for Valkey serverless can complement databases for caching. The article points specialized graph, time-series, and document workloads to corresponding services, and names Neptune for connected-data needs in agentic applications. These are opinionated starting points; the article says to match the choice to access patterns, scale, and operational constraints.

## Source excerpt

Database selection is a foundational decision when building an application. Choosing the right database enables you to focus effort on building customer value while the database scales with demand. AWS offers several fully managed database services. That breadth serves the diversity of the millions of customers who operate databases on AWS, but it raises a practical question: Where do I start? Based on our collective experience working with database customers, this post provides a direct, opinionated answer focused on the job you are trying to perform: migrating an existing workload, refactoring a legacy application, or building something new.