AWS助理架构师认证培训 | AWS Fundamentals RDS + Aurora + ElastiCache

视频来源：B站《AWS 认证解决方案架构师 助理级 SAA-C03》

一边学习一边整理老师的课程内容及试验笔记，并与大家分享，侵权即删，谢谢支持！

附上汇总贴：AWS助理架构师认证培训 | 汇总_热爱编程的通信人的博客-CSDN博客

---

Amazon RDS Overview

Amazon RDS Overview

• RDS stands for Relational Database Service
• lt's a managed DB service for DB use SQL as a query language
• lt allows you to create databases in the cloud that are managed by AWS Postgres MySQL MariaDB Oracle Microsoft SQL Server Aurora (AWS Proprietary database)

Advantage over using RDS versus deploying DB on EC2

• RDS is a managed service:Automated provisioning, OS patching Continuous backups and restore to specifc timestamp (Point in Time Restore)!Monitoring dashboardsRead 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)
• BUT you can't SSH into your instances

RDS - Storage Auto Scaling

• Helps you increase storage on your RDS DB instance dynamically
• When RDS detects you are running out of free database storage, it scales automatically
• Avoid manually scaling your database storage
• You have to set Maximum Storage Threshold (maximum limit for DB storage)
• Automatically modify storage if:Free storage is less than 10% of allocated storageLow-storage last at least 5 minutes6 hours have passed since last modifcation
• Useful for applications with unpredictable workloads
• Supports all RDS database engines (Maria DB, MySQL, PostgreSQL, SQLServer, Oracle)

RDS Read Replicas vs Multi AZ

RDS Read Replicas for read scalability

• Up to 5 Read Replicas
• Within AZ, Cross AZ or Cross Region
• Replication is ASYNC, so reads are eventually consistent
• Replicas can be promoted to their own DB
• Applications must update the connection string to leverage read replicas

RDS Read Replicas - Use Cases

• 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)

RDS Read Replicas - Network Cost

• In AWS there's a network cost when data goes from one AZ to another
• For RDS Read Replicas within the same region, you don't pay that fee

RDS Multi AZ (Disaster Recovery)

• SYNC replication
• 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
• Note: The Read Replicas be setup as Muti AZ for Disaster Recovery (DR)

RDS - From Single-AZ to Multi-AZ

• Zero downtime operation (no need to stop the DB)
• Just click on "modify" for the database
• The following happens internally:A snapshot is takenA new DB is restored from the snapshot in a new AZSynchronization is established between the two databases

RDS Custom for Oracle and Microsoft SQL Server

RDS Custom

• Managed Oracle and Microsoft SQL Server Database with OS and database customization
• RDS: Automates setup, operation, and scaling of database in AWS
• Custom: access to the underlying database and OS so you can Configure settingsInstall patchesEnable native featuresAccess the underlying EC2 Instance using SSH or SSM Session Manager
• De-activate Automation Mode to perform your customization, better to take a DB snapshot before
• RDS vs. RDS CustomRDS: entire database and the OS to be managed by AWSRDS Custom: full admin access to the underlying OS and the database

Amazon Aurora

Amazon Aurora

• Aurora is a proprietary technology from AWS (not open sourced)
• Postgres and MySQL are both supported as Aurora DB (that means your drivers will work as if Aurora was a Postgres or MySQL database)
• Aurora is "AWS cloud optimized" and claims 5x performance improvement over MySQL on RDS, over 3x the performance of Postgres on RDS
• Aurora storage automatically grows in increments of 10GB, up to 128TB
• Aurora can have 15 replicas while MySQL has 5, and the replication process is faster (sub 10 ms replica lag)
• Failover in Aurora is instantaneous. It's HA native
• Aurora costs more than RDS (20% more) - but is more efficient

Aurora High Availability and Read Scaling

• 6 copies of your data across 3 AZ:4 copies out of 6 needed for writes 3 copies out of 6 need for readsSelf healing with peer-to-peer replicationStorage is striped across 100s of volumes
• One Aurora Instance takes writes (master)
• Automated failover for master in less than 30 seconds
• Master + up to 15 Aurora Read Replicas serve reads
• Support for Cross Region Replication

Aurora DB Cluster

Features of Aurora

• 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

Amazon Aurora - Advanced Concepts

Aurora Replicas - Auto Scaling

Aurora - Custom Endpoints

• Define a subset of Aurora Instances as a Custom Endpoint
• Example: Run analytical queries on specific replicas
• The Reader Endpoint is generally not used after defining Custom Endpoints

Aurora Serverless

• 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 Multi-Master

• In case you want immediate failover for write node(HA)
• Every node does RW - vs promoting a RR as the new master

Global Aurora

• Aurora Cross Region Read Replicas:Useful for disaster recoverySimple to put in place
• Aurora Global Database (recommended):1 Primary Region (read/write)Up to 5 secondary (read-only) regions, replication lag is less than 1 secondUp to 16 Read Replicas per secondary regionHelps for decreasing latencyPromoting another region (for disaster recovery) has an RTO of < 1 minuteTypical cross-region replication takes less than 1 second

Aurora Machine Learning

• Enables you to add ML-based predictions to your applications via SQL
• Simple, optimized, and secure integration between Aurora and AWS ML services
• Supported servicesAmazon SageMaker (use with any ML model)Amazon Comprehend (for sentiment analysis)
• You don't need to have ML experience
• Use cases: fraud detection, ads targeting, sentiment analysis, product recommendations

RDS & Aurora - Backup and Monitoring

RDS Backups

• Automated backups:Daily full backup of the database (during the maintenance window)Transaction logs are backed-up by RDS every 5 minutes =>ability to restore to any point in time (from oldest backup to 5 minutes ago)1 to 35 days of retention, set 0 to disable automated backups
• Manual DB Snapshots Manually triggered by the user Retention of backup for as long as you want
• Trick: in a stopped RDS database, you will still pay for storage. If you plan on stopping it for along time, you should snapshot & restore instead

RDS & Aurora Restore options

• Restoring a RDS / Aurora backup or a snapshot creates a new database
• Restoring MySQL RDS database from S3Create a backup of your on-premises databaseStore it on Amazon S3 (object storage)Restore the backup file onto a new RDS instance running MySQL
• Restoring MySQL Aurora cluster from S3Create a backup of your on-premises database using Percona XtraBackupStore the backup file on Amazon S3Restore the backup file onto a new Aurora cluster running MySQL

Aurora Database Cloning

• Create a new Aurora DB Cluster from an existing one
• Faster than snapshot & restore
• The new DB cluster uses the same cluster volume and data as the original but wil change when data updates are made
• Very fast & cost-effective
• Useful to create a "staging" database from a "production" database without impacting the production database

RDS Security

RDS & Aurora Security

• At-rest encryption:Database master & replicas encryption using AWS KMS - must be defined as launch timelf the master is not encrypted, the read replicas can not be encryptedTo encrypt an un-encrypted database, go through a DB snapshot & restore as encrypted
• In-flight encryption: TLS-ready by default, use the AWS TLS root certificates client-side
• IAM Authentication: IAM roles to connect to your database (instead of username/pw)
• Security Groups: Control Network access to your RDS / Aurora DB
• No SSH available except on RDS Custom
• Audit Logs can be enabled and sent to CloudWatch Logs for longer retention

RDS Proxy

Amazon RDS Proxy

• Fully managed database proxy for RDS
• 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, auto scaling, highly available (multi-AZ)
• Reduced RDS & Aurora failover time by up 66%
• Supports RDS (MySQL, PostgreSQL, Maria DB) and Aurora (MySQL, PostgreSQL)
• No code changes required for most apps
• Enforce lAM Authentication for DB, and securely store credentials in AWS Secrets Manager
• RDS Proxy is never publicly accessible (must be accessed from VPC)

ElasticCache Overview

Amazon ElastiCache Overview

• The same way RDS is to get managed Relational Databases...
• ElastiCache is to get managed Redis or Memcached
• 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
• Using ElastiCache involves heavy application code changes

ElastiCache Solution Architecture - DB Cache

• Applications queries ElastiCache, if not available, get from RDS and store in ElastiCache
• Helps relieve load in RDS
• Cache must have an invalidation strategy to make sure only the most current data is used in there

ElastiCache Solution Architecture - User Session Store

• User logs into any of the application
• The application writes the session data into ElastiCache
• The user hits another instance of our application
• The instance retrieves the data and the user is already logged in

ElastiCache - Redis vs Memcached

REDIS

• Multi AZ with Auto-Failover
• Read Replicas to scale reads and have high availability
• Data Durability using AOF persistence
• Backup and restore features

MEMCACHED

• Multi-node for partitioning of data (sharding)
• No high availability (replication)
• Non persistent
• No backup and restore
• Multi-threaded architecture

ElasticCache for Solution Architects

ElastiCache - Cache Security

• All caches inElastiCache:Do not support IAM authentication IAM policies on ElastiCache are only used for AWS API-level security
• Redis AUTHYou 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 fight encryption
• MemcachedSupports SASL-based authentication (advanced)

Patterns for ElastiCache

• Lazy Loading: all the read data is cached, data can become stale in cache
• Write Through: Adds or update data in the cache when written to a DB (no stale data)
• Session Store: store temporary session data in a cache (using TTL features)
• Quote: There are only two hard things in Computer Science: cache invalidation and naming things

ElastiCache - Redis Use Case

• Gaming Leaderboards are computationally complex
• Redis Sorted sets guarantee both uniqueness and element ordering
• Each time a new element added, it's ranked in realtime, then added in correct order