Basic Information
| Field | Details |
|---|---|
| English name | Amazon Aurora |
| Full name | Amazon Aurora |
| Chinese description | AWS 云原生关系型数据库 |
| Japanese description | クラウドネイティブリレーショナルデータベース |
| Exam frequency | ⭐⭐⭐⭐⭐ |
| Often confused with | RDS 常规引擎 / DynamoDB |
In one sentence
Aurora preserves SQL and transaction semantics while using distributed storage across three AZs for durability, availability, and read scaling.
Core purpose
- Cluster storage keeps six copies across three AZs; that does not mean six database instances.
- One writer handles writes, and up to 15 Aurora replicas can scale reads and join failover.
- The cluster endpoint targets the writer; the reader endpoint balances across readers.
Exam focus
- MySQL/PostgreSQL compatibility plus cloud-native high performance and availability point to Aurora.
- Aurora Global Database supports cross-Region reads and disaster recovery, not ordinary Multi-AZ.
- Serverless v2 adjusts compute capacity but does not remove database-design or cost management.
Common misconceptions
- Aurora does not support every RDS database engine.
- Fifteen replicas means reader instances, not fifteen independent storage copies.
Key takeaway
MySQL/PostgreSQL compatibility + distributed cloud-native storage + multiple readers → Aurora.
Related services
RDS, Global Database, AWS Backup, DMS, Secrets Manager.