Skip to main content - Aurora runs only in AWS infrastructure.
- Aurora is MySQL compatible, and can provide 5-times better performance than MySQL.
- Aurora can deliver High Availability and performance.
- Aurora provides better Scaling.
- Aurora starts with 10GB and can scales in 10GB increments to 64 TB (Storage Auto Scaling)
- Compute resource can upscale to 32v CPUs and 244 GB of Memory.
- Aurora maintains two copies of the data in each AZ and maintains 3 AZ, so total 6 copies of the data.
- Aurora is designed to handle transparently the loss of up to two copies of data without impacting the write availability and up to three copies without impacting the read availability.
- Aurora is a self-healing, Data blocks and disks are continuously scanned for errors and repaired automatically.
- Two types of Replicas for Aurora
- Aurora Replicas (currently 15)
- MySQL read Replicas (Currently 5)
- Replicas priority login works in Tier 0 > Tier 1 > …. > Tier 15.
- DB Cluster Identifier will be the DNS end point for the database instance.
- Replication instance will have the DNS name as end point. In case of failure of the Cluster end point, it will automatically use the replication instance end point, no need to update the connection string.
- AWS database types
- Elastic Cache – In Memory Cache
- Encryption of the Database
- Encryption at REST is supported for MySQL, Oracle, SQL, PostgreSQL, MariaDB and Aurora.
- Encryption is done by AWS KMS service (Key Management Service).
- Once the RDS instance is encrypted. The data stored at REST in the underlying storage is encrypted.
- This is applicable for Automated, Read Replicas and Snapshots.
- At present, Encryption of the existing database is not supported. To use Amazon RDS encryption for the existing database, you must first create a snapshot, make a copy of that snapshot and encrypt the copy.