Database
CoreAmazon Aurora
AWS-built relational database compatible with MySQL or PostgreSQL that separates distributed cluster storage from compute.
Key points
- Aurora uses a writer and optional replicas against shared cluster storage; reader endpoints distribute eligible reads.
- Replicas can serve reads and be promoted, while Global Database patterns address cross-Region reads and recovery requirements.
- Choose it from engine compatibility, topology, performance, availability, and cost—not a generic claim that it is always faster.
Best-known use cases
- Run compatible relational applications needing managed high availability and read scaling.
- Build an Aurora cross-Region topology when RPO, RTO, and read locality justify it.
What candidates often confuse it with
- Aurora offers an AWS-built compatible cluster architecture; standard RDS offers a wider set of managed engines.
- Provisioned Aurora supplies fixed capacity; Aurora Serverless scales supported database capacity.
Key takeaway
Choose Aurora when its compatible engines and distributed cluster architecture match the workload.
Related services
- Amazon RDS
- Amazon Aurora Serverless
- Amazon RDS Proxy
- Amazon ElastiCache
Relevant exam tasks
- D2.2
- D3.3
- D4.3