AWS Databases
AWS database services are managed offerings covering relational, key-value, document, graph, time-series, and in-memory workloads. They handle provisioning, patching, backups, and replication so teams can focus on schema design and query patterns rather than infrastructure.
itCloud computing | OpenSkills.info
Intro
AWS Databases
AWS Databases is a portfolio, not one database. The services use different data models and operating models. Your first task is to match the workload to a model, not to pick the most familiar product name.
Start with the data and the questions the application asks. Relational databases organize structured data into tables and support joins. Key-value databases optimize access through known keys. Document databases store JSON-like records. Graph databases make relationships central. Time-series databases organize measurements around time.
AWS calls this purpose-built database selection. One application can use more than one database type when its parts have different access patterns. That choice can improve fit, but every added database creates another schema, security boundary, failure mode, and operating surface.
Choose the data model before the service
Write down the workload before comparing products:
- What entities and relationships must you represent?
- Which reads and writes happen most often?
- Which queries are known in advance, and which must remain flexible?
- Which transactions require strict consistency across several records?
- What latency, throughput, availability, and recovery targets apply?
- How quickly can traffic and stored data grow?
- Which engine features or client protocols must remain compatible?
The answers narrow the field.
| Data model | AWS starting point | Typical fit |
|---|---|---|
| Relational | Amazon RDS or Amazon Aurora | Structured records, joins, flexible queries, and multi-row transactions |
| Key-value | Amazon DynamoDB | Known access patterns, large scale, and predictable low-latency requests |
| Document | Amazon DocumentDB | JSON-like documents and queries across document fields |
| In-memory | Amazon ElastiCache or Amazon MemoryDB | Caching, session data, and workloads that need very low latency |
| Graph | Amazon Neptune | Relationship traversal, fraud graphs, recommendations, and knowledge graphs |
| Time series | Amazon Timestream | Measurements, events, metrics, and queries organized by time |
| Wide-column | Amazon Keyspaces | Cassandra-compatible workloads with high throughput and low latency |
| Vector | Several AWS database and search services | Similarity search over vector representations |
Amazon Redshift serves analytical data-warehouse workloads. It belongs in the wider data platform, but it is not the default answer for an online transaction path.
Continue the course
This section is part of the paid course.
See pricing to subscribe, or log in if you already have access.
Where this skill leads
Relevant careers
See how this topic contributes to broader role-level skill maps.
Sources
- https://docs.aws.amazon.com/databases-on-aws-how-to-choose/
Supports
- AWS provides relational, key-value, document, in-memory, graph, time-series, wide-column, and vector database options
- Relational services support structured data, joins, and flexible query patterns
- DynamoDB, DocumentDB, Neptune, Timestream, Keyspaces, ElastiCache, and MemoryDB map to distinct workload and data-model needs
- One application can combine best-fit database types
- Amazon Redshift targets analytical data-warehouse workloads rather than the default OLTP path
- Serverless database options scale capacity and use pay-for-use models
- https://aws.amazon.com/products/databases/
Supports
- AWS maintains a portfolio of managed and purpose-built database services
- AWS database services provide service-specific availability, security, scaling, and vector capabilities
- Managed database services reduce common database infrastructure administration
- https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/Welcome.html
Supports
- RDS supports Db2, MariaDB, Microsoft SQL Server, MySQL, Oracle Database, and PostgreSQL
- RDS manages common tasks including installation, patching, backups, failure detection, and recovery
- Customers retain responsibility for database design, query tuning, monitoring, identities, and workload-specific behavior
- RDS supports Multi-AZ deployments, read replicas, VPC placement, CloudWatch monitoring, and several storage and billing models
- https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/CHAP_AuroraOverview.html
Supports
- Aurora is a managed relational database compatible with MySQL and PostgreSQL
- Aurora clusters separate shared storage from database compute
- Aurora provides cluster endpoints for connection roles and service-specific scaling and availability features
- https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/Introduction.html
Supports
- DynamoDB is a serverless fully managed NoSQL database
- DynamoDB supports key-value and document data models
- Primary key design controls item identification and data distribution
- DynamoDB provides on-demand and provisioned capacity modes, consistency options, backups, and global tables
- https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/Concepts.MultiAZSingleStandby.html
Supports
- A single-standby RDS Multi-AZ DB instance deployment uses synchronous replication to another Availability Zone
- RDS can fail over to the standby for high availability
- A single standby does not serve read traffic and is not a read-scaling mechanism
- Synchronous replication can increase write and commit latency
- https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_ReadRepl.html
Supports
- RDS DB instance read replicas are read-only copies used to reduce read load
- RDS DB instance read replicas receive primary changes asynchronously and can expose stale data
- Read replicas and Multi-AZ standbys have different purposes and replication behavior
- Read replicas can be promoted and can support cross-Region recovery patterns
- https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/USER_WorkingWithAutomatedBackups.html
Supports
- RDS creates automated backups during the backup window and retains them for the configured period
- RDS supports point-in-time recovery within the backup retention period
- Manual snapshots have a lifecycle independent from automated backups
- Backup deletion and retention behavior depends on database deletion choices
- https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/Overview.Encryption.html
Supports
- RDS encryption at rest covers storage, logs, automated backups, read replicas, and snapshots
- RDS uses AWS KMS keys and supports AWS-managed or customer-managed keys
- Disabling or losing access to a KMS key can make encrypted RDS resources inaccessible
- Key choice and key policy belong in database protection and recovery planning
- https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/MonitoringOverview.html
Supports
- RDS integrates with CloudWatch metrics and alarms
- RDS provides Performance Insights and Enhanced Monitoring
- RDS monitoring includes connections, read and write operations, storage, CPU, memory, network traffic, logs, and events
- Monitoring supports reliability, availability, and performance work but requires workload-specific interpretation
- https://docs.aws.amazon.com/whitepapers/latest/aws-risk-and-compliance/shared-responsibility-model.html
Supports
- AWS and customers share security and compliance responsibilities
- AWS operates the infrastructure from the host operating system and virtualization layer through physical facilities
- Customer responsibilities vary with the selected service and include configured controls, applications, data, and compliance requirements
- https://docs.aws.amazon.com/dms/latest/userguide/Welcome.html
Supports
- AWS DMS discovers sources, converts schemas, and migrates relational, warehouse, NoSQL, and other data stores
- DMS supports one-time migration and ongoing replication
- DMS Fleet Advisor builds an inventory for migration planning
- DMS migrations use source and target endpoints and replication tasks
- https://docs.aws.amazon.com/dms/latest/userguide/schema-conversion.html
Supports
- DMS Schema Conversion assesses heterogeneous migration complexity
- DMS Schema Conversion converts schemas and many database code objects to a target-compatible format
- Conversion reports identify objects that require manual action
- Converted code can be reviewed, saved, edited, or applied to the target
