Please enable JavaScript.

Coggle requires JavaScript to display documents.

RDS, Aurora, ElastiCache - Coggle Diagram

- - - - Free storage < 10%
      - Low storage last >= 5 min
      - Last modification > 6 hours ago
      - All engines supported
  - - - Eventual consistency
    - - Reporting on production data without affecting performance
    - - Cross AZ traffic free for RDS
      - Only cross region traffic has costs
  - - - Snapshot taken
      - New DB restored from snapshot in new DB
      - Sync established between the two DBs
  - - - Oracle
      - MS SQL Server
    - - Configure settings
      - Install patches
      - Enable native features
      - SSH access to EC2
      - Full admin access on OS
  - - - Daily full backups
      - Transaction logs every 5 minutes
        
        Point-In-Time-Restore (PITR)
      - 1 - 35 days retention
    - - Trigger snapshot
      - Indefinite retention
    - - Backup and restore snapshot
      - Much cheaper than keeping EBS when DB not used
  - - - Create backup of on-prem
      - Transfer to S3
      - Restore backup file to new MySQL RDS
- - - - PostgreSQL
      - MySQL
    - - 5x MySQL RDS performance
      - 3x PostgreSQL RDS performance
    - - Increments of 10GB
      - Max 128TB
  - - - 4/6 needed to write
      - 3/6 needed to read
      - Self-healing with p2p replication
      - Storage striped across 100s volumes
    - - Sub 10ms replication lag
    - - App only needs to use 1 writer and 1 reader endpoint
  - - - Good for DR
    - - 1 Primary read/write region
      - Up to 5 read only regions
      - Up to 16 read replicas per region
      - Replication lag < 1s
      - Useful for low latency
      - Promote read only region to primary in < 1 minute
  - - - SageMaker
      - Comprehend
    - - Fraud detection
      - Ads targeting
      - Sentiment analysis
      - Product recommendations
  - - - Cannot be disabled
      - 1 - 35 days retention
      - PITR during retention period
    - - Trigger snapshot
      - Indefinite retention
  - - - Create on-prem backup with Percona XtraBackup
      - Transfer backup file to S3
      - Restore backup file to new MySQL Aurora cluster
  - - - Clone starts by using same storage as original
      - Any writes copies data to new storage and modifies it there
    - - Create staging DB from production
- - - - Uses KMS
      - Read replicas cannot be encrypted if master is not
      - DB snapshot & restore to encrypt / decrypt DB
    - - TLS by default
      - AWSTLS root cert on client-side
    - - Can use IAM roles to connect to DB
      - Instead of username / password
    - - Control network access to DB
    - - Except RDS custom
    - - Can be enabled
      - Send to CloudWatch for longer retention
  - - - RDS
        
        MySQL
        
        PostgreSQL
        
        MariaDB
        
        MS SQL Server
      - Aurora
        
        MySQL
        
        PostgreSQL
- - - - Multi-AZ
      - Auto failover
      - Read replicas to scale reads & HA
      - Data durability using AOF
      - Backup & restore
      - Supports sets & sorted sets
    - - Multi-node for data partitioning (sharding)
      - No HA
      - Non persistent
      - No backup & restore
      - Multi-threaded
  - - - Password set on cluster creation
      - Supports SSL
    - - Supports SASL based auth
  - - - All data read is cached
      - Cached data can become stale
    - - Add / update cache on write
      - No stale data
    - - Store session data in cache
      - Use TTL