Mastering AWS Aurora: Next-Gen Database - 2023 (24 labs)

Set up an AWS account by following sign-up steps, create the initial root user, then switch to a safer user, and delete unused resources to avoid charges.

Navigate an AWS account to manage Aurora and RDS databases, explore regions like North Virginia, create a database, and use Cost Explorer to forecast monthly costs.

Set up an aurora vpc with three subnets across availability zones, an internet gateway and route table, and a security group permitting port 3603 for aurora.

Understand how AWS Aurora versions differ from MySQL and Postgres engines, with unique version numbers and release cycles, and identify available versions—typically the latest appears first.

Explore how Amazon Aurora database instance classes determine cpu and memory, including serverless v2, memory-optimized, and burstable options with Graviton processors and unlimited mode bursts.

Amazon Aurora uses a cluster volume on SSDs, replicating data across three availability zones for durability, high availability, and fast failover, with local storage for non-persistent sorting and indexing.

Understand how the Aurora cluster volume stores all data and metadata, enabling auto-growing storage independent of the instance and charging only for the space you use up to 128 TB.

Learn how Aurora ensures reliability with multi-AZ storage, six data copies across three availability zones, automatic storage auto repair, survivable page cache, and crash recovery for fast, durable performance.

Explore how Aurora provides high availability through multi-AZ replication, six storage nodes, and failover to read replicas, plus global databases and RDS proxy resilience.

Aurora delivers fault-tolerant storage across multiple zones with automatic failover to a promoted replica or a new primary, usually within 60–120 seconds, and supports a multi-AC configuration for seamless continuity.

Discover how Amazon Aurora handles replication with built-in cross-availability-zone replication and options like Aurora Global Database or MySQL/PostgreSQL replication, and how to add replicas.

Leveraging Amazon Aurora replicas, distribute read traffic across up to 15 read-only replicas, using the reader endpoint to scale reads while the primary writer handles writes and ensures quick failover.

Explore replication options for Aurora MySQL, including global databases, cross-region replicas via MySQL bin log, up to five read replicas per region, and same-region clusters.

Explore replication options for Aurora PostgreSQL, including Aurora Global Database for multi-region scaling, up to five regional replicas, and note that Aurora Plus does not support cross-regional replication.

Overview of Amazon AWS Aurora MySQL, compare MySQL and PostgreSQL, and learn to create a cluster via the AWS management console. Connect with MySQL Workbench and consider related charges.

Download and install MySQL Workbench, a free visual tool for database architects, developers, and DBAs. Connect it to the Aurora database on AWS to begin managing your data.

Create an Aurora MySQL database cluster, connect to it, add a replica, and delete the cluster afterward to avoid charges.

Connect to an AWS Aurora MySQL database cluster using writer and reader endpoints, then set up a MySQL Workbench connection with host, port 3306, admin, and password, and test it.

Add an Aurora reader for an existing database in same region, in B availability zone, with public access and enhanced monitoring; connect to the reader endpoint as a read-only replica.

Demonstrates deleting an AWS Aurora MySQL cluster by removing writer and reader instances, skipping a final snapshot, and preserving VPC subnets and security groups for future databases.

Explore Aurora global databases spanning multiple regions for low-latency reads and rapid recovery. See how a single primary region writes data and replicates to read-only secondary regions.

Create an Amazon Aurora global database by selecting global features, choosing non-production, memory-optimized r6g large instances, then add a second region with global right forwarding for MySQL.

Explore Amazon Aurora global databases, where the primary cluster handles writes while read-only secondaries in other regions reduce latency for worldwide apps, with planned or manual failover options.

Explore how Aurora global database provides local latency for global reads across regional offices. Scale secondary clusters with read-only replicas and quickly fail over to a secondary region during outages.

Learn how a headless Amazon Aurora database cluster operates without a database instance, decoupling compute and storage to lower costs, enabling a global database across regions.

Demonstrates deleting a headless instance from the secondary reader of a global database, skipping a final snapshot, and monitoring the deletion as the headless instance disappears.

Configure an aurora global database that spans at least two regions, with memory-optimized ar5 or higher writer and secondary read-only replicas, supporting five secondary regions and unique names across regions.

Connect to the reader endpoint for read-only requests in your region of the global database. Connect to the main endpoint for read-write operations; minimize latency by choosing the closest region.

Modify the aurora global database by configuring each cluster's parameter groups independently, while keeping consistent settings across regions to avoid inconsistencies when promotion occurs.

Remove a cluster from an aws aurora global database by detaching replicas and the primary, turning it into a standalone, read-write cluster, with a demo afterward.

Remove a secondary cluster from a headless Aurora Global Database to convert it into a non-global, single-region database.

Explore how Aurora global database enables cross-region failover to minimize downtime and data loss, comparing manual unplanned and managed planned failovers with recovery time objective and recovery point objective considerations.

Upgrade an Aurora global database using standard procedures for an Aurora cluster. Upgrade both primary and secondary clusters to the major, minor, and patch versions to ensure safe failover.

Learn how to delete an AWS Aurora global database and its components, starting from the bottom up with clusters and instances, across regions to avoid ongoing costs.

Aurora automatically backs up your cluster with a retention of one to 35 days in S3, enabling continuous incremental backups and point-in-time restores; extend with snapshots or AWS Backup.

Explore how Amazon Aurora handles automated backups within a backup window, backups continue when needed and avoid overlap with the weekly maintenance window; learn to copy backups to extend retention.

Explore recovering Aurora data via backups or snapshots, point-in-time restore, cloning with minimal space, and backtrack for MySQL, plus cost considerations.

Demonstrates creating an Amazon Aurora database, taking a manual snapshot named my sql snap one, and viewing progress under snapshots; it covers exporting to S3, restoring, copying, and sharing snapshots.

Copy and share an AWS Aurora snapshot, rename it, copy tags and encryption settings, and share with another account using a non-default encryption key.

Discover how to restore an Amazon Aurora snapshot to spin up a new database, set a new name, VPC access, security groups, instance class, and options like parameter groups.

Demonstrates exporting an Aurora database snapshot to S3 by creating an S3 bucket and KMS key, configuring a new export role, and initiating the export to S3.

Delete an Amazon Aurora database snapshot and S3 exports, cancel and clean up backups to avoid extra costs.

Explore how Aurora serverless v2 provides on-demand auto scaling that adjusts capacity with demand, removing manual sizing. Learn about pay-for-what-you-use pricing and setting min and max capacity.

Discover Aurora serverless use cases and version two for variable workloads, including multitenant applications, mixed workloads, development testing, with readers scaling independently and paying only for what you use.

Discover how Aurora serverless automatically scales compute resources based on a minimum and maximum capacity you specify, with storage remaining separate from compute for workloads like retail, gaming, and reports.

Create an Aurora cluster by mixing Aurora Serverless and provisioned capacity for a mixed configuration, or run a cluster entirely on Aurora Serverless as reader traffic scales.

Explain Aurora serverless capacity in RCU, show how writers and readers scale within a min and max range, and illustrate load-driven up and down scaling.

Establish high availability with Amazon Aurora Serverless across multiple availability zones, enabling automatic failover and scalable standby capacity, with up to 15 serverless readers.

Aurora serverless and provisioned storage both use six copies of data across three availability zones. Replication keeps data safe when compute capacity changes, and storage remains unaffected by compute failures.

Configure Aurora clusters for serverless and provisioned capacity, including mixed configurations, and learn how capacity parameters apply to writers and readers, with buffer cache memory automatically scaling.

Navigate AWS console to create an Aurora serverless database, selecting MySQL compatibility, configuring min and max ACUs, enabling read replicas, VPC, security, logs, backtrack, and maintenance, then create and connect.