Search⌘ K
AI Features

Introduction to Amazon Aurora

Explore the fundamental concepts of Amazon Aurora, a managed relational database service that separates compute and storage for high availability and scalability. Learn about Aurora's cluster architecture, instance roles including writers and readers, endpoint routing for seamless failover, and data protection methods such as backups, snapshots, and cloning. This lesson prepares you to make informed design decisions and supports AWS certification objectives.

Organizations running relational workloads on MySQL or PostgreSQL often hit a ceiling where a single database instance cannot deliver the availability, durability, and read scaling they need without significant operational overhead. Standard Amazon RDS deployments attach storage to individual instances, replicate asynchronously to read replicas, and require manual volume resizing as data grows. Amazon Aurora addresses these constraints by redesigning how compute and storage interact inside a fully managed relational database service that remains wire-compatible with MySQL and PostgreSQL. Understanding Aurora’s cluster-based model is essential for AWS certification scenarios and for making sound architectural decisions in production because Aurora changes the rules around failover speed, replica lag, storage management, and data protection.

Aurora belongs to the Amazon RDS family, yet it is not simply “RDS with a different label.” It decouples compute from storage by introducing a shared distributed storage layer called the cluster volume.A single, auto-scaling virtual volume that spans three Availability Zones and maintains six copies of your data, managed entirely by Aurora rather than by individual database instances. This separation means that database instances read from and write to the same pool of durable storage instead of each maintaining a private copy on Amazon EBS.

The primary unit of deployment is an Aurora DB cluster, which consists of one or more DB instances plus the cluster volume. Aurora ships in two distinct engine families. Aurora MySQL-Compatible Edition tracks community MySQL versions such as 5.7 and 8.0, while Aurora PostgreSQL-Compatible Edition tracks PostgreSQL versions 13 through 16, depending on the release. The engine family you choose at cluster creation time determines your SQL dialect, supported extensions, parameter defaults, and access to Aurora-specific features.

This lesson covers the cluster model, instance roles, endpoint routing, engine families at a high level, and data protection basics, including backups, snapshots, and cloning. These concepts prepare you for the deeper architectural dive in the next lesson, Amazon Aurora Core Architecture.

The following diagram illustrates how an Aurora DB cluster organizes its writer instance, reader instances, and shared cluster volume across three Availability Zones:

Amazon Aurora DB cluster architecture separating compute instances from a six-copy, three-AZ shared cluster volume that auto-scales up to 128 TiB
Amazon Aurora DB cluster architecture separating compute instances from a six-copy, three-AZ shared cluster volume that auto-scales up to 128 TiB

With the high-level cluster picture in place, the ...