Login Get started

AWS Relational Database Service RDS Masterclass | AWS RDS Full Course | RDS Zero to Hero | AWS Demo

A Monk in Cloud ☁️・2 minutes read

AWS RDS master class covers databases, types, reasons to run on EC2 vs. not, importance of RDS features, setup steps for MariaDB on EC2, billing, creating databases, monitoring, backups, maintenance, and migrating from EC2 to RDS. The master class explains Multi-AZ, replication, backups, read replicas, and their impact on RPO and RTO, with more topics to be covered in future videos.

Insights

Running databases on EC2 instances offers benefits like OS access, advanced tuning, and specific database versions, but comes with drawbacks such as admin overhead and backup challenges.
Setting up an RDS database involves creating a subnet group, selecting settings like database type and storage, and enabling features like monitoring and automated backups, with costs displayed upfront and a crucial endpoint provided for database connection.

Get key ideas from YouTube videos. It’s free

Recent questions

What are the advantages of using AWS RDS?
AWS RDS offers benefits like managed database services, various database support, and cost-effective billing.
How can databases be created in AWS RDS?
Databases in AWS RDS can be created by selecting database type, version, and settings, followed by configuring security groups and monitoring options.
What is the process of migrating databases to RDS from EC2?
Migrating databases to RDS from EC2 involves taking a dump, connecting to RDS, and verifying data transfer for seamless transition.
What is the significance of RDS Multi-AZ option?
RDS Multi-AZ provides high availability through standby replicas in different availability zones, ensuring data redundancy and failover protection.
How do RDS read replicas enhance database performance?
RDS read replicas improve performance by redirecting read operations to replicas, reducing the load on the primary instance and enhancing scalability.

Related videos

Summary

00:00

AWS RDS Master Class: Database Hosting Advantages

Weekend master class on AWS RDS service announced
Comprehensive coverage from basics to advanced topics
Overview of databases, types, and relational vs. non-relational
Databases on EC2 instances architecture explained
Three-tier architecture: web server, application, and database
Risks of running all components on one EC2 instance
Reasons to run databases on EC2 instances: OS access, advanced tuning, vendor demands, specific database versions, and operating systems
Reasons not to run databases on EC2 instances: admin overhead, backup and disaster recovery challenges, single availability zone risk, missed opportunities with AWS RDS
Importance of utilizing AWS RDS features and products
Advantages of using AWS RDS for database hosting and management

18:49

Maximize benefits with effective EC2 database hosting

Utilize available options effectively to avoid missing out on benefits
Upgrade skills and setup time to monitor EC2 instances for database hosting
Strong Linux and operating system knowledge required for running databases on EC2
Continuous monitoring and troubleshooting essential for EC2 instance maintenance
Performance may be slower when running databases on EC2 compared to AWS options
Demonstration on hosting a MariaDB database on an EC2 instance in AWS console
Understanding the process aids in appreciating time saved by using RDS
Migration of databases from EC2 to RDS instance demonstrated for learning
Detailed steps provided for installing and configuring MariaDB on an EC2 instance
Overview of RDS as a managed database service supporting various databases like MySQL, MariaDB, PostgreSQL, Oracle, and Microsoft SQL, including Amazon Aurora.

36:34

"Setting up RDS databases in AWS"

RDS billing is per instance and hourly rate for compute and storage.
Billing for storage is based on the allocated storage consumed.
RDS instances can be created in the AWS console.
A subnet group needs to be created before setting up an RDS database.
Subnets within availability zones need to be selected for the subnet group.
Database creation method can be standard or easy, with easy using recommended configurations.
Database type, version, and template need to be selected during creation.
Settings like database identifier, master username, password, instance class, and storage type must be specified.
Public access and VPC security group settings are crucial for database accessibility.
Additional configurations include monitoring, automated backups, and maintenance windows for the RDS instance.

53:58

Database Maintenance, Protection, and Monitoring Essentials

To enable maintenance, select a window or let the system choose one for you, allowing for maintenance activities.
Deletion protection prevents accidental database deletion; enabling it restricts database deletion.
Estimated monthly costs are displayed before creating the database, aiding in cost estimation.
After creating the database, the status will show as "creating" until completion.
The database creation process may take some time, with the status eventually changing to "available."
The database endpoint is crucial for connecting to the database, remaining constant even after restarts.
Configuration details include database instance ID, class, RAM, vCPU, engine version, and storage size.
Monitoring provides CPU utilization, free space, read/write IOPS, and memory details.
Logs and events store all activity logs related to the database instance.
Migrating an existing database from an EC2 instance to an RDS involves taking a dump, connecting to the RDS, and verifying data transfer.

01:11:39

"RDS Multi-AZ: High Availability, Standby Replicas"

Migrating an existing database from an EC2 instance to a MariaDB database on RDS involves creating a standby replica in another availability zone.
RDS Multi-AZ option creates a standby replica in a different availability zone for high availability.
Standby replica in Multi-AZ has its own storage in the same availability zone as the primary instance.
RDS databases can only be accessed using canonical names or endpoints.
Synchronous replication in Multi-AZ ensures simultaneous write operations in both primary and standby replicas.
Automatic failover in Multi-AZ occurs within 60 to 120 seconds if the primary instance fails.
Multi-AZ feature incurs extra infrastructure costs and standby replicas cannot be accessed directly.
RDS Multi-AZ offers high availability but not fault tolerance, with some downtime during failover.
RPO (Recovery Point Objective) is the time between the last backup and a failure, influencing technical solutions and costs.
RTO (Recovery Time Objective) is the time between a disaster recovery event and full recovery, influenced by processes, staff, and documentation.
RDS backups start with a full snapshot and subsequent snapshots are incremental, with brief interruptions during snapshots.
Manual snapshots do not expire and must be cleaned up manually, while automatic backups can be configured for retention periods.
Restoring a database creates a new RDS instance with a new endpoint address, influencing RPO values.
RDS read replicas are asynchronous and can be created in the same or different regions for performance improvements and scalability.
Read replicas improve performance by allowing redirection of read operations to replicas, reducing impact on write operations and IOPS.

01:30:32

Impact of Replication, Snapshots, and Backups

Replication in Cross region does not affect RTO (Recovery Time Objective), while snapshots and backups impact RPO (Recovery Point Objective) by reducing the time difference between the last backup and failure occurrence. Three replicas do not enhance any RDO (Recovery Data Objective). Additional topics related to RDS will be covered in separate videos due to the length of this master class. Subscribe to the channel for more content on AWS relational database services.

Try it yourself — It’s free.