RDS Flashcards
1
Q
What is the best way to instantiate RDS quickly
A
Restore from a snapshot: the database will have schemas and data ready!
2
Q
What is the best way to instantiate EBS quickly
A
Restore from a snapshot: the disk will already be formatted and have data!
3
Q
What does RDS stand for??
A
Relational Database Service
4
Q
What Databases do RDS support (6)
A
- Postgres
- MySQL
- MariaDB
- Oracle
- Microsoft SQL Server
- Aurora (AWS Proprietary database)
5
Q
- 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)
A
RDS
6
Q
Can you SSH into your RDS instance??
A
NO
7
Q
- Helps you increase storage on your RDS DB instance dynamically
- When RDS detects you are running out of free database storage, it scales automatically
A
RDS – Storage Auto Scaling
8
Q
You have to set ____________ (maximum limit for DB storage)
A
Maximum Storage Threshold
9
Q
RDS – Storage Auto Scaling automatically modify storage if _____ (3)
A
- Free storage is less than 10% of allocated storage
- Low-storage lasts at least 5 minutes
- 6 hours have passed since last modification
10
Q
RDS – Storage Auto Scaling is Useful for applications with ____________
A
unpredictable workloads
11
Q
Does RDS - Storage Auto Scaling support all RDS database engines??
A
YES
……….
MariaDB
MySQL
PostgreSQL
SQL Server
Oracle
12
Q
How many read replicas can an RDS instance have
A
up to 15 replicas
13
Q
Can you have RDS in Within AZ, Cross AZ or Cross Region
A
YES
14
Q
What type of replication does RDS have?
A
Async
15
Q
Can RDS replicas be promoted to their own DB??
A
YES
16
Q
Applications must update the __________ to leverage read replicas
A
connection string
17
Q
- You have a production database that is taking on normal load
- You want to run a reporting application to run some analytics
- You create a Read Replica to run the new workload there
- The production application is unaffected
- Read replicas are used for SELECT (=read) only kind of statements (not INSERT, UPDATE, DELETE)
A
RDS Read Replicas – Use Cases
18
Q
Is there a cost, in AWS, when data goes from one AZ to another??
A
YES
19
Q
Is there a cost, in AWS, for RDS Read Replicas within the same region??
A
NO
20
Q
What type of replication does RDS Multi AZ (Disaster Recovery) have??
A
SYNC
21
Q
- One DNS name – automatic app failover to standby
- Increase availability
- Failover in case of loss of AZ, loss of network, instance or storage failure
- No manual intervention in apps
- Not used for scaling
A
RDS Multi AZ (Disaster Recovery)
22
Q
What is the downtime to switch from a single AZ to a multi-AZ??
A
0 downtime
23
Q
What happens internally when you switch from single AZ to a multi AZ??
A
- A snapshot is taken
- A new DB is restored from the snapshot in a new AZ
- Synchronization is established between the two databases
24
Q
Managed Oracle and Microsoft SQL Server Database with OS and database customization
A
RDS Custom
25
Allows you access to the underlying database and OS so you can
* Configure settings
* Install patches
* Enable native features
* Access the underlying EC2 Instance using SSH or SSM Session Manager
RDS Custom
26
Aurora is “AWS cloud optimized” and claims 5x performance improvement over _________ on RDS, over 3x the performance of _________ on RDS
MySQL
Postgres
27
Aurora storage automatically grows in increments of _________, up to ________.
10GB
128 TB
28
What is Aurora's replica lag time???
sub 10ms
29
Are Failovers in Aurora is instantaneous????
YES
30
Does Aurora cost more?? If so, how much more??
YES.
20%
31
6 copies of your data across 3 AZ:
* 4 copies out of 6 needed for writes
* 3 copies out of 6 need for reads
* Self healing with peer-to-peer replication
* Storage is striped across 100s of volumes
RDS Aurora
32
Automated failover for master in less than _________
30 seconds
33
Can RDS Aurora support Cross Region Replication
YES
34
* Automatic fail-over
* Backup and Recovery
* Isolation and security
* Industry compliance
* Push-button scaling
* Automated Patching with Zero Downtime
* Advanced Monitoring
* Routine Maintenance
* Backtrack: restore data at any point of time without using backups
Features of Aurora (9)
35
* Automated database instantiation and auto- scaling based on actual usage
* Good for infrequent, intermittent or unpredictable workloads
* No capacity planning needed
* Pay per second, can be more cost-effective
Aurora Serverless
36
* In case you want continuous write availability for the writer nodes
* Every node does R/W - vs promoting a Read Replica as the new master
Aurora Multi-Master
37
* Useful for disaster recovery
* Simple to put in place
Aurora Cross Region Read Replicas:
38
* 1 Primary Region (read / write)
* Up to 5 secondary (read-only) regions, replication lag is less than 1 second
* Up to 16 Read Replicas per secondary region
* Helps for decreasing latency
* Promoting another region (for disaster recovery) has an RTO of < 1 minute
* Typical cross-region replication takes less than 1 second
Aurora Global Database (recommended):
39
Enables you to add ___________ predictions to your applications via SQL
Aurora Machine Learning
40
What are 2 supported services by Aurora Machine learning?
* Amazon SageMaker (use with any ML model)
* Amazon Comprehend (for sentiment analysis)
41
Are RDS Backups Automated??
YES
42
How often are full RDS backups taken??
Daily (During the backup window)
43
Transaction logs are backed-up by RDS every __________ minutes
5
44
Doe you have the ability to restore RDS to any point in time??
YES
45
How to disable RDS backups??
Set retention to 0
46
What is the retention of Manual DB snapshots??
As long as you want
47
Trick: in a stopped RDS database, you will still pay for storage. If you plan on stopping it for a long time, you should snapshot & restore instead
48
Aurora Backups -
* 1 to 35 days (cannot be disabled)
* point-in-time recovery in that timeframe
Automated backups
49
Aurora Backups -
* Manually triggered by the user
* Retention of backup for as long as you want
Manual DB Snapshots
50
Restoring a RDS / Aurora backup or a snapshot creates a _______?
new database
51
Restoring MySQL RDS database from S3 (3)
* Create a backup of your on-premises database
* Store it on Amazon S3 (object storage)
* Restore the backup file onto a new RDS instance running MySQL
52
Restoring MySQL Aurora cluster from S3 (3)
* Create a backup of your on-premises database using Percona XtraBackup
* Store the backup file on Amazon S3
* Restore the backup file onto a new Aurora cluster running MySQL
53
* Create a new Aurora DB Cluster from an existing one
* Faster than snapshot & restore
* Uses copy-on-write protocol
* Initially, the new DB cluster uses the same data volume as the original DB cluster (fast and efficient – no copying is needed)
* When updates are made to the new DB cluster data, then additional storage is allocated and data is copied to be separated
* Very fast & cost-effective
* Useful to create a “staging” database from a “production” database without impacting the production database
Aurora Database Cloning
54
RDS & Aurora Security -
* Database master & replicas encryption using AWS KMS – must be defined as launch time
* If the master is not encrypted, the read replicas cannot be encrypted
* To encrypt an un-encrypted database, go through a DB snapshot & restore as encrypted
At-rest encryption:
55
RDS & Aurora Security ... TLS-ready by default, use the AWS TLS root certificates client-side
In-flight encryption
56
IAM roles to connect to your database (instead of username/pw)
IAM Authentication
57
Control Network access to your RDS / Aurora DB
Security Groups
58
Is SSH available for RDS / Aurora?
No, but it is for RDS Custom
59
RDS & Aurora Security - Audit Logs can be ________ and sent to _______ for longer retention
enabled
CloudWatch Logs
60
* Fully managed
* Allows apps to pool and share DB connections established with the database
* Improving database efficiency by reducing the stress on database resources (e.g., CPU, RAM) and minimize open connections (and timeouts)
* Serverless, autoscaling, highly available (multi-AZ)
* Reduced RDS & Aurora failover time by up 66%
* Supports RDS (MySQL, PostgreSQL, MariaDB, MS SQL Server) and Aurora (MySQL, PostgreSQL)
* No code changes required for most apps
* Enforce IAM Authentication for DB, and securely
store credentials in AWS Secrets Manager
* Is never publicly accessible (must be accessed from VPC)
Amazon RDS Proxy
61
* Caches are in-memory databases with really high performance, low latency
* Helps reduce load off of databases for read intensive workloads
* Helps make your application stateless
* AWS takes care of OS maintenance / patching, optimizations, setup, configuration, monitoring, failure recovery and backups
Amazon ElastiCache Overview
62
Amazon ElastiCache Overview managed which to Cache services?
Redis and Memcached
63
* Multi AZ with Auto-Failover
* Read Replicas to scale reads and have high availability
* Data Durability using AOF persistence
* Backup and restore features
* Supports Sets and Sorted Sets
REDIS
64
* Multi-node for partitioning of data (sharding)
* No high availability (replication)
* Non persistent
* No backup and restore
* Multi-threaded architecture
MEMCACHED
65
ElastiCache supports IAM Authentication for ________
Redis
66
IAM policies on ElastiCache are only used for?
AWS API-level security
67
* You can set a “password/token” when you create a
Redis cluster
* This is an extra level of security for your cache (on top of security groups)
* Support SSL in flight encryption
Redis AUTH
68
Supports SASL-based authentication (advanced)
Memcached
69
Patterns for ElastiCache (3)
Lazy Loading
Write Through
Session Store
70
Patterns for ElastiCache - all the read data is cached, data can become stale in cache
Lazy Loading
71
Patterns for ElastiCache - Adds or update data in the cache when written to a DB (no stale data)
Write Through
72
Patterns for ElastiCache - store temporary session data in a cache (using TTL features)
Session Store
73
