Please enable JavaScript.

Coggle requires JavaScript to display documents.

AWS Virtual Private Cloud (VPC) Virtual/logical datacentre in the cloud…

- - - - ACL
      - Torrent
    - - S3 Glacier Deep Archive
      - S3 - Intelligent Tiering
        
        Machine learning
      - S3 One Zone - IA
      - S3 Standard
      - S3 Glacier
      - S3 - IA (Infrequently accessed)
    - - Website endpoint
    - - Destination region
      - Replication entire bucket / prefix or tags
      - Delete marker not replicated
        or individual versions
      - Doesn't replicate existing objects, only new ones
      - Requires versioning enabled
    - - At Rest
        
        Client-side
        
        KMS-managed customer master key
        
        client-side master key
        
        Server-side
        
        S3-Managed Keys (SSE-S3)
        
        AES 256
        
        KMS-managed keys (SSE-KMS)
        
        Customer-provided keys (SSE-C)
      - In Transit
        
        SSL / TLS
    - - Enables applications to retrieve only a subset of data from an object
    - - Use a distinct URL to upload directly to an edge location which then gets transferred to S3
        *.s3-accelerate.amazonaws.com
      - 20GB file size, same as CloudFront
      - Utilises the CloudFront Edge Network
  - - - Databases
        
        RDS (Relational Database Service) OLTP (Online Transaction Processing)
        
        MySQL
        
        Max size 16TB
        
        Read Replicas
        
        Scaling not DR!
        
        Can have read replicas that have Multi-AZ
        
        Can create read replicas of multi AZ source databases
        
        Read replicas can be promoted to be their own DB. This breaks the replication
        
        Can have read replicas of read replicas (watch out for latency)
        
        Can have up to 5 read replica-copies of any DB
        
        Can have read replica in a second region
        
        Each read replicas will have its own DNS end point
        
        Read replicas primarily for very read-heavy DB workloads
        
        Read-only copy of DB
        
        Uses asynchronous replication
        
        Must have automatic backups turned on in order to deploy a read replica
        
        Available for:
        MySQL Server
        PostgreSQL
        MariaDB
        Aurora
        
        Can be in any region
        
        Aurora
        
        2 types of replicas available
        Aurora replicas (currently 15)
        MySQL Read Replicas
        
        Can handle loss of up to two copies of data without affecting DB write availability
        3 copies without affecting read availability
        
        2 copies contained in each AZ
        Min 3 AZ, 6 copies of data
        
        Sing instance Failover - Creates a new DB in the same AZ. If unable to do so will place in different AZ
        
        Replicas
        
        MySQL replicas
        
        Aurora replicas
        
        Automated failover only available with Aurora replicas
        
        Failover is automatically handled
        
        Backups
        
        Can take snapshots
        
        Can share snapshots with other AWS accounts
        
        Automated backups are always enabled.
        
        Do not impact DB perofrmance
        
        Start with 10GB, scales in 10GB increments to 64TB (Storage autoscaling)
        
        Compute resources can scale up to 32vCPUs & 244GB of memory
        
        Replica failover, uses this instead of creating new DB
        
        Flips the CNAME record
        
        Read
        
        SQL
        
        PostgreSQL
        
        Test
        
        Multi-AZ
        
        DB instance failure, RDS will automatically failover to the standby
        
        AWS updates the IP of the endpoint automatically
        
        Can force a failover from one AZ to another by rebooting the RDS instance
        
        Allows to have an exact copy of your DB in another AZ
        
        AWS handles the replication, new data is written to the standby DB
        
        For DR only
        
        Available for:
        SQL Server
        Oracle
        MySQL Server
        PostgreSQL
        MariaDB
        
        Encryption at rest
        
        Supported for:
        MySQL
        Oracle
        SQL server
        PostgreSQL
        MariaDB
        Aurora
        
        Underlying storage is encrypted, as are its automated backups, read replicas & snapshots
        
        Disabled by default
        
        Uses AWS KMS
        
        Backups
        
        Automated
        
        Enabled by default
        
        Backup stored in S3
        
        Free storage equal to the size of DB. DB size 50GB, free 50GB of storage
        
        Retention period - 1 and 35 days
        
        Restores > Choose the most recent daily backup, and then applies the relevant transaction log to that day
        
        Point in time recovery down to a second, within the retention period
        
        Stores transaction logs throughout the day
        
        Taken within a define window
        
        During the window storage I/O may be suspended while data is being backed up and may experience elevated latency
        
        Full daily snapshot
        
        Database snapshots
        
        Manually
        
        Stored even after you delete the original RDS instance, unlike automated backups
        
        The restored version of the DB will be a new RDS instance with a new DNS endpoint
        
        DynamoDB - No SQL
        
        Spread across 3 geographically distinct data centres
        
        Stored on SSD storage
        
        RDS requires bigger instance size or add read replica
        
        Push button scaling
        
        Eventual consistent reads (Default)
        
        Across all copies of data is usually reached within a second. Repeating a read after a short time should return the updated data (Best read performance)
        
        DynamoDB Accelerator (DAX)
        
        Does all the heavy lifting required to add in-memory acceleration into DynamoDB tables
        
        In-memory cache that delivers up to 10x performance improvement
        
        Real time bidding, social gaming & trading applicaitons
        
        Strongly consistent reads
        
        Read returns a result that reflects all writes that received a successful response prior to the read
        
        Fasty & flexible NoSQL DB
        
        Great fit for mobile, web gaming, ad-tech, IoT & many other applications
        
        RedShift - OLAP (Online Analytical Processing)
        
        Multi-Node
        
        Compute node - up to 128
        
        Store data and perform queries & computations
        
        Leader Node
        
        Managers client connections & receives queries
        
        Single node (160GB)
        
        Spectrum
        
        Petabyte of data
        
        Data warehousing
        
        Used for business intelligence
        
        Priced
        
        Billed 1 unit per node per hour, so a 3-node data warehouse cluster running persistency for an entire month would incur 2,160 instance hours
        
        Compute Node Hours
        
        Data transfer (only within a VPC, not outside it)
        
        Not charged for leader node hours, only compute nodes will incur charges
        
        Security considerations
        
        By default RedShift takes care of key management
        
        AWS Key Management Service
        
        Can manage your own keys through HSM
        
        Encrypted in transit using SSL
        
        Encrypted at rest using AES-256 encryption
        
        Advanced compression
        
        Columnar data stores can be compressed much more than row-based data stores because similar data is stored sequentially on disk
        
        Backups
        
        Redshift always attempts to maintain at least three copies of your data (the original & replica on the compute nodes and a backup in Amazon S3)
        
        Can also asynchronously replicate your snapshots to S3 in another region for disaster recovery
        
        Enabled by default with a 1 day retention period
        
        Maximum retention period is 35 days
        
        Availability
        
        Currently only available in 1 AZ
        
        Can restore snapshots to new AZs in the event of an outage
        
        Massively Parallel Processing (MMP)
        
        Automatically distributes data & query load across all nodes. Redhsift makes it easy to add nodes to data warehouse & enables you to maintain fast query performance as the data grows
        
        ElasticCache - In memory caching
        
        Redis
        
        Popular open-source in-memory key-value store
        
        Multi-AZ
        
        Backup & Restore
        
        Memcached
        
        Existing tools will work with Memcache
        
        Simple & easy to deploy
        
        Can scale horizontally
        
        Increase database and web application performance
        
        Neptune
        
        Fast, reliable, fully-managed graph database service
        
        Milliseconds latency
        
        AWS Schema Conversion Tool
        
        Convert the source schema and code to match the target
        
        Database migration Service