Please enable JavaScript.

Coggle requires JavaScript to display documents.

AWS - Coggle Diagram

- - - - SSE-S3: Keys handled & managed by Amazon S3
        Object is encrypted server side
        Must set header: "x-amz-server-side-encryption":"AES256"
      - SSE-KMS: Keys handled & managed by KMS
        Object is encrypted server side
        Must set header: "x-amz-server-side-encryption":"aws:kms"
      - SSE-C: Keys fully managed by the customer outside of AWS
      - Client side encryption
        Clients must encrypt data themselves before sending to S3.
        Clients must decrypt data themselves when retrieving from S3.
        Customer fully manges the keys and encryption cycle
    - - Cross Region Replication (CRR)
        Use cases: compliance, lower latency access, replication across accounts
      - Same Region Replication (SRR)
        Use cases: log aggregation, live replication, between production and test accounts
    - - S3 Standard
      - S3 Intelligent Tiering
      - S3 Standard - Infrequent access (IA)
      - S3 One Zone - IA
      - S3 Glacier
      - S3 Glacier Deep Archive
    - - Transaction actions
        Move objects from a class to another class after N days
      - Expiration actions
        Delete objects after N days
  - - - General Purpose SSD (gp2, gp3)
        General purpose SSD volume that balances price and performance for a wide variety of workloads
        Can be used as boot volume
        Volume size: 1 GiB - 16 TiB
        1GiB = 3 IOPS
        Min/Max IOPS: 100 - 16000
        Small gp2 volume can burst IOPS to 3000
        If volume size is 5334 GiB, we are at the max IOPS. If volume size > 5334, IOPS is still 16000
      - Provisioned IOPS SSD (io1, io2)
        Highest-performance SSD for mission critical low latency or high throughput workloads
        Can be used as boot volume
        Volume size: 4 GiB - 16 TiB
        1GiB = 50 IOPS
        Min/Max IOPS: 100 - 64000 (Nitro instances) else 32000 (other instances)
        The maximum ratio of 50:1 is permitted between IOPS and volume size
      - Cold HDD (sc1)
        Lowest cost HDD volume designed for less frequently access workloads
        Volume size: 125 GiB - 16 TiB
        IOPS: Not applicable
        Throughput: 1 TiB = 12 MB/s
        Max throughput: 250 MB/s
      - Throughput Optimized HDD (st1)
        Low cost HDD volume designed for frequently accessed, throughput extensive workloads
        Volume size: 125 GiB - 16 TiB
        IOPS: Not applicable
        Throughput: 1 TiB = 40 MB/s
        Max throughput: 500 MB/s
      - Magnetic (standard)
        Volume size: 1 GiB - 1024 TiB
    - - RAID 0 (Increase performance)
        Combine 2 or more volumes and getting the total disk space and I/O.
        But one disk fails, all the data is failed.
        Use cases: An application that needs a lot of IOPS and doesn't need fault-tolerance; A DB that has replication already built-in.
        Using this, we can have a very big disk with a lot of IOPS.
        For example:
        2 volumes x 500GiB (4000 IOPS) will create 1 x 1000 GiB (8000 IOPS)
      - RAID 1 (Increase fault tolerance)
        Mirroring a volume to another.
        If one disk fails, our logical volume is still working.
        We have to send the data to 2 EBS volumes at the same time (2x network).
        Use case: Application that need increase volume fault tolerance.
  - - - Cached Volumes
        Low-latency access to your most recently used data.
      - Stored volumed
        On-premises data with scheduled offsite backups
- - - - Security Group
        Is stateful: Return traffic is automatically allowed, regardless of any rules
- - - - Reader Endpoint
        Connection Load Balancing
        Auto Scaling Read Replicas
      - Write Endpoint
        Pointing to the master (Writing)
    - - One writer and multiple readers
        Supports multiple reader instances connected to the same storage volume as a single writer instance. This is a good general-purpose option for most workloads.
      - One writer and multiple readers - Parallel Query
        Improves the performance of analytic queries by pushing processing down to the Aurora storage layer. This is a good option for hybrid transactional/analytic workloads
      - Multiple writers
        Supports multiple writer instances connected to the same storage volume. This is a good option for when continuous writer availability is required.
      - Serverless
        You specify the minimum and maximum amount of resources needed, and Aurora scales the capacity based on database load. This is a good option for intermittent or unpredictable workloads
- - - - CNAME: hostname to hostname
        Only work for non root domain
        ex: something.mydomain.com
      - AAAA: hostname to IPv6
        Works for ROOT and NON ROOT DOMAIN
        ex: mydomain.com
      - A: hostname to IPv4
        Works for ROOT and NON ROOT DOMAIN
        ex: mydomain.com
- - - - CloudFront distributions
      - Regional resources (ALB, API Gateway, AppSync)