Amazon Aurora (MySQL /

PostgreSQL)
 Amazon Aurora

 Amazon Aurora is a relational database service developed and offered by Amazon Web Services
(AWS) that is compatible with MySQL and PostgreSQL.
 It's designed to handle enterprise-level database workloads, delivering up to five times the
throughput of standard MySQL and three times the throughput of standard PostgreSQL.
 at 1/10th the cost.
 Aurora is fully managed by Amazon RDS, which automates time-consuming administration tasks
like hardware provisioning, database setup, patching, and backups.
 Amazon Aurora Features

 Highly Durable and Available :

 Aurora is designed to offer greater than 99.99% availability.
 Replicating 6 copies of your data across 3 Availability Zones.
 It continuously backs up your data to Amazon S3.
 Transparently recovers from physical storage failures.
 instance failover typically takes less than 30 seconds.

 Scalability :
 scale database read capacity to handle high-volume applications by creating up to 15 low-latency read
replicas within or across multiple regions.
 It can also automatically scale the compute resources up and down based on the capacity needs of
your workload.
 Amazon Aurora Features

 Security :
 Network isolation using Amazon VPC.
 Encryption at rest using keys you create .
 Control through AWS Key Management Service (KMS).
 Encryption of data in transit using Secure Sockets Layer (SSL).

 Compatible with MySQL and PostgreSQL :

 Most of the code, applications, drivers, and tools you already use today with your existing databases can
be used with Aurora with little or no change.
 Fully Managed :
 Amazon Aurora automates common administrative tasks like database setup, patching, and backups,
freeing up your time to focus on your application.
 Amazon Aurora Architecture

 Storage :
 Aurora automatically divides your database volume into 10GB segments spread across many disks.
 Each chunk of your database volume is replicated six times across three Availability Zones.
 Aurora storage is fault-tolerant, transparently handling the loss of up to two copies of data without affecting write
availability and up to three copies without affecting read availability.
 Aurora storage is also self-healing; data blocks and disks are continuously scanned for errors and replaced
automatically.

 Replication :
 Aurora allows up to 15 Aurora Replicas to be created, which share the same underlying volume as the primary
instance.
 This means the replicated data is available almost instantaneously, and failover is very fast compared to the
standard MySQL or PostgreSQL engines.
 The replicas can offload read traffic from your primary database instance.
 Amazon Aurora Architecture

 End Points :
 Aurora uses endpoints to allow your applications to connect to an Aurora DB cluster.
 There are three main types of endpoints: cluster endpoint, reader endpoint, and instance endpoint.
 The cluster endpoint connects to the current primary DB instance for that DB cluster.
 The reader endpoint load-balances connections to the Aurora Replicas in a DB cluster.
 Instance endpoint connects to a specific DB instance within a DB cluster.
 Fail Over Handling :
 Aurora allows up to 15 Aurora Replicas to be created, which share the same underlying volume as the
primary instance.
 This means the replicated data is available almost instantaneously, and failover is very fast compared to
the standard MySQL or PostgreSQL engines.
 The replicas can offload read traffic from your primary database instance.
 Amazon Aurora Architecture

 Backup and Recovery :

 Aurora continuously backs up your data to Amazon S3.
 you can restore your database from these backups at any point within the backup retention period.
 Also use the AWS Management Console, AWS CLI, or RDS API to create a snapshot of your DB cluster at
any time.
 Serverless Option:
 Amazon Aurora Serverless is an on-demand, auto-scaling configuration.
 Aurora automatically starts up, scales compute capacity to match your application’s usage, and shuts
down during periods of inactivity.
 This makes it a good option for unpredictable workloads.