RDS Flashcards
Which databases are supported by RDS?
Postgres, MySQL, MariaDB, Oracle, MS SQL Server, Aurora (AWS proprietary Database)
How many read replicas can you have in Aurora?
you can have 15 replicas, while MySQL has five. The replication process is faster.
How Aurora ensures high availability?
there are 6 copies of your data across 3 AZ.
- 4 copies out of 6 needed for writes
- 3 copies out of 6 needed for reads
- self-healing with peer-to-peer replication
What’s the advantage of using RDS over deploying databases on EC2?
- Automated provisioning, OS patching
- Continuous backups and restore to specific timestamp (Point in Time Restore)!
- Monitoring dashboards
- Read replicas for improved read performance
- Multi-AZ setup for DR (Disaster Recovery)
- Maintenance windows for upgrades
- Scaling capability (vertical and horizontal)
- Storage backed by EBS (gp2 or io1)
- Automated Backup
But you cannot SSH into the instance.
What is storage autoscaling in RDS?
RDS storage autoscaling helps you increase the storage on your DB instance dynamically. When RDS detects you are running out of free database storage, it scales automatically. You have to set the maximum storage threshold so your database does not grow infinitely. This is useful for applications with unpredictable workloads.
How many read replicas can be there in RDS?
There can be up to 5 read replicas
Can RDS read replicas be in the same AZ?
The replicas can be within the same AZ, cross AZ or cross-region
Are replicas in-sync with the main RDS DB instance?
The replication to replicas is asynchronous, but they are eventually consistent
What is the use of RDS read replicas?
Replicas provide better performance for reading the data from the RDS for the stop it can be used by the reporting or any analytical tool that only needs to read the data.
Replicas can be promoted to their own DB. Applications must update the connection string to leverage the read replicas
Is there a network cost when data goes from one AZ to another?
The data synchronization between same or different AZ free. But there is a cost when data is synchronized across regions. Data synchronization within the same region is free but It’s not free between different regions.
How is disaster recovery configured in RDS?
The disaster recovery is configured across the AZs (Multi-AZ) with synchronous replication (instantly). One DNS name is configured for the application to the main RDS database instance. In the event of failure, the automation failover will occur and DNS will point to the DR instance. There won’t be any interruption in the application. The DR instance becomes the master DB Instance.
The DR instance cannot be used for scaling (no one can read or write to it, it’s just here for the failover if anything goes wrong with the master database).
Read Replicas can be setup as a Multi-AZ for disaster recovery (DR). It’s a common exam question.
Can RDS be changed from a single AZ to multiple AZ?
The RDS settings can be modified to make the database from a single AZ to multiple AZ. Behind the scene, AWS will take that snapshot of the master instance and restore it in the new AZ. A synchronization is set up between the master and the standby DB instances.
What is the difference between RDS and RDS custom?
In RDS, the entire database at the OS is managed by AWS.
In RDS custom, you have access to the database and the OS. You don’t have control over the hardware. You also have access to the EC2 instance. RDS custom is available only for Oracle and Microsoft SQL Server. You can customize the instance or the database. But you must disable the automation mode before you perform any customization.
Aurora is compatible with which databases?
It’s compatible Postgres and MySQL
What is the writer endpoint and reader endpoint in Aurora DB?
The writer endpoint is a DNS name that is used for writing the data to the master DB instance. In case of failure, the writer endpoint may point to the read replica and promote it as a master DB instance. The application pointing to the master DB instance would not require any change.
Reader endpoint is also a DNS name used by the applications to read the data from the read replicas. The Aurora database automatically performs the auto-scaling, and new replicas are set up to ensure the desired performance.
Is it possible to backtrack data in Aurora?
Yes the database can be restored at any point of time without using backup put a stop. Aurora uses a different method to do that.
What is Aurora replicas autoscaling?
If there are multiple read requests AWS creates more replicas depending upon the higher CPU usage of the existing read replicas.
What are Aurora’s custom endpoints?
The custom endpoints provide load balancing and high availability for each group of DB instances within your cluster. If one of the DB instances within a group becomes unavailable, Aurora directs subsequent custom endpoint connections to one of the other DB instances associated with the same endpoint.
The custom endpoints can be created to run analytical queries or any other specific purpose. These read replicas can be larger instances compared to other existing replicas.
What is Aurora serverless?
Amazon Aurora Serverless is an on-demand, autoscaling configuration for Amazon Aurora. It automatically starts up, shuts down, and scales capacity up or down based on your application’s needs. You can run your database on AWS without managing database capacity.
Manually managing database capacity can take up valuable time and can lead to inefficient use of database resources. With Aurora Serverless, you create a database, specify the desired database capacity range, and connect your applications. You pay on a per-second basis for the database capacity that you use when the database is active, and migrate between standard and serverless configurations with a few steps in the Amazon Relational Database Service (Amazon RDS) console.
What is Aurora multi-master?
Most kinds of Aurora clusters are single-master clusters. For example, provisioned, Aurora Serverless, parallel query, and Global Database clusters are all single-master clusters. In a single-master cluster, a single DB instance performs all write operations and any other DB instances are read-only. If the writer DB instance becomes unavailable, a failover mechanism promotes one of the read-only instances to be the new writer.
In a multi-master cluster, all DB instances can perform write operations. The notions of a single read/write primary instance and multiple read-only Aurora Replicas don’t apply. There isn’t any failover when a writer DB instance becomes unavailable, because another writer DB instance is immediately available to take over the work of the failed instance. We refer to this type of availability as continuous availability, to distinguish it from the high availability (with brief downtime during failover) offered by a single-master cluster