• Amazon Relational Database
    • Database
      • Tables
        • Rows
        • Columns
    • Database Engines
      • Supported with Amazon Aurora, MariaDB, MSSQL, MySQL, Oracle, and PostgreSQL
    • Key Features
      • Multi-AZ (for disaster recovery)
        • Supported with MariaDB, MSSQL, MySQL, Oracle, and PostgreSQL
        • Synchronous replication
      • Read Replicas (for performance)
        • Supported with Amazon Aurora, MariaDB, MySQL, Oracle, and PostgreSQL
        • Asynchronous replication
        • Up to five read replicas
        • Each replica has it’s own DNS endpoint address
        • You may have read replicas of read replicas
        • May be promoted to a standalone database (breaks replication)
    • Components
      • Connection string (db.abc.us-east-1.rds.amazonaws.com)
    • Backups
      • Automated backups (enabled by default)
        • Retention period between one and thirty five days
        • Daily backup and transaction logs for point in time recovery down to a second within the retention period
      • Database snapshots
        • Manual
      • Restoring Backups
        • The restored version will be a new RDS instance with a new DNS endpoint
    • Encryption at Rest
      • Supported with Amazon Aurora, MariaDB, MSSQL, MySQL, Oracle, and PostgreSQL
      • Uses AWS KMS
  • Amazon DynamoDB
    • Database
      • Collection | Table
      • Document | Row
      • Key Value Pairs | Fields
    • Stored on SSD storage
    • Spread across three geographically distinct data centers
    • Read Models
      • Eventual consistent reads (default and best read performance)
      • Strongly consistent reads
  • Amazon Redshift
    • Configuration
      • Single Node (160 GB)
      • Multi-Node
        • Leader node – Manages client connections and receives queries
        • Compute node – Store data and perform queries (up to 128)
    • Massive Parallel Processing – Automatically distributes data and query load across all nodes
    • Backups
      • Enabled by default (with a one day retention period)
      • Maximum retention period is 35 days
      • Redshift attempts to maintain at least three copies of your data (original and replica on the compute nodes and a backup in S3)
      • Can asynchronously replicate snapshots to S3 in another region for disaster recovery
    • Security
      • Data is encrypted in transit using SSL
      • Data is encrypted at rest using AES-256 encryption
      • By default, Redshift manages key management
        • You may manage your own keys using HSM
        • You may manage your own keys using AWS KMS
    • Availability
      • Only available in one AZ
      • Can restore snapshots to new AZs in the event of an AZ outage
  • Amazon Aurora
    • MySQL and PostgreSQL compatible relational database engine
    • Start with 10 GB and may scale in 10 GB increments to 64 TB (storage autoscaling)
    • Compute resources can scale up to 32 vCPUs and 244 GB of RAM
    • Two copies of your data are contained in each availability zone with a minimum of three availability zones for six copies of your data
    • Scaling
      • Designed to transparently handle the loss of up to two copies of data without affecting database write availability and up to three copies without affect read availability
      • Storage is self-healing
    • Aurora Read Replicas
      • Aurora replicas (up to 15 with automated failover)
      • MySQL read replicas (up to 5 with no automated failover)
    • Backups
      • Automated backups enabled by default (do not impact database performance)
      • You may take snapshots (do not impact performance)
      • You may share Aurora snapshots with other AWS accounts