Aurora
Last updated
Last updated
NOT open-sourced,
Postgres & MySQL are both supported as Aurora DB
auto grows (10GB up to 128GB)
5x performance over MySQL on RDS, over 3x performance of Postgres on RDS.
Aurora can have 15 replica, while MySQL has 5, and the replication process is faster.
Failover is instantaneous. It's HA (High Availability) natively.
Cost 20% more than RDS.
Define a subset of Aurora instances as Custom Engdpoint
Ex: run analytical queries on specific replicas
Provides load-balancing for read-only connections.
Reduces overhead on primary instance by using Aurora Replicas for read operations.
Scales capacity for handling simultaneous SELECT queries based on the number of Aurora Replicas.
Way to offload READ traffic.
Share the same underlying traffic as the primary DB -> lag time is low.
Read Replica DB have their own endpoint -> the app need to be configured to direct READ traffic to that endpoint.
Supported services
SageMaker (ML model)
Comprehend (for sentiment analysis)
Use cases: fraud detection, ads targeting, sentiment analysis, product recommendations.
Automated backups
1 to 35 days (cannot be disabled)
point-in-time recovery in that timeframe
Manually backups (the same as RDS)
Manually triggered by user
Retention of backup for as long as you want
Restoring MySQL Aurora cluster from S3
Create a backup of your on-premises database using Percona XtraBackup
Store the backup file on Amazon S3
Restore the backup file onto the new Aurora cluster running MySQL
Clone a new Aurora cluster from an existing one.
Benefit
Fast
Cost-effective
Use case: you want to create a staging Aurora from production Aurora. Instead of create a snapshot -> restore, it's faster if you clone it.
for high availability, durability
no single point of failure
upto 6 storage notes in 3 AZs.
Available for MySQL-compatible edition of Aurora
Endpoint: connections to Aurora are managed through endpoints, serving as intermediaries, to handle database connections.
