Please enable JavaScript.

Coggle requires JavaScript to display documents.

CPU Credit &placement (dedicated host and dedicated instance…

- - - - Cluster – clusters instances into a low-latency group in a single AZ
        
        features
        
        is aLOGICAL GROUPING of instances within a SINGLE AZ
        
        don’t span across Availability Zones
        
        recommended for applications that benefits from low network latency, HIGH NETWORK THROUGHPUT or both.
        
        To provide the lowest latency, and the highest packet-per-second network performance for the placement group,
        
        instances can be added later, but there are chances of encountering an insufficient capacity error
        
        instances can be added later, but there are chances of encountering an insufficient capacity error
        
        Can launch a new instance from the AMI into a placement group.
        
        stopping and starting an instance within the placement group, the instance still runs in the same placement group
        
        is only available within a single AZ either in the same VPC or PEER VPC
        
        is more of an hint to AWS that the instances need to be launched physically close to each together
        
        enables applications to participate in a low-latency, 10 Gbps network.
        
        Used case:HPC
      - Partition – s
        
        feature
        
        is a group of instances spread across partitions. Partitions are logical groupings of instances,
        
        can be used to spread deployment of large distributed and replicated workloads, such as HDFS, HBase, and Cassandra database , across distinct hardware to reduce the likelihood of correlated failures
        
        HBASE
        
        Provide read/write access to your Big Data
        
        HDFS
        
        Hadoop Distributed File System ( HDFS
        
        same partition share same underlying hardware across different underlying hardware
        
        diff partiton share different rack
        
        MAX maximum of 7 PARTITIONS per Availability Zone
        
        The number of instances that you can launch in a partition placement group is limited only by your account limits.
        
        can span multiple Availability Zones in the same Region(same as Spread cluster)
        
        are not supported for Dedicated Hosts
        are currently only available through the API or AWS CLI.
        
        defintion
        
        preads instances across logical partitions,
        
        ensuring that instances in one partition do not share underlying hardware with instances in other partitions
        
        SAME partition same hardware
        
        MAx is 7 partition groups
      - Spread – spreads instances across underlying hardware
        
        feature
        
        MAx is 7 instances per spread group
        
        is a group of instances that are each placed onDISTINCT underlying hardware
        
        recommended for applications that have a small number of critical instances that should be kept separate from each other.
        
        Further reduce the risk of simultaneous failures that might occur when instances share the same underlying hardware.
        
        provide access to distinct hardware, and are therefore suitable for mixing instance types or launching instances over time.
        
        can span multiple AZs, and can have a maximum of seven running instances per AZ PER GROUP
        
        If the start or launch an instance in a spread placement group fails cause of insufficient unique hardware to fulfill the request, the request can be tried later as EC2 makes more distinct hardware available over time
        
        are not supported for Dedicated Instances or Dedicated Hosts.
        
        diagram
- - - - Current price for Unused Ec2
    - - your bidding price
    - - You specify criteria
        
        AWS choose from instance pool and assign base on your criteria
        
        Criteria specification
        
        Target capacity
        
        VPCU, Memeory, storage & Bandwidth
        
        Based on instance type
    - - Unused EC2 based on same instance type and OS
    - - EX: your spot price request is 1 dollar, and spot price is < 1 or = 1, Spot instance assigned t o you
        
        If your spot price > your spot price request, EC2 wtermianted wthin half an hour.
    - - Spot price > sport price request
      - If AWS run out of Spot instance capacity
- - - - Want to shutdown test Ec2 during week end and after hour office
- - - - Pre-requiste
        
        Must be EBS back root-voluem
        
        Memory must save in EBS root volume
        
        RAM contents are encrypted in EBS
      - use same start and stop API
- - - - Used when u lost your key pair
      - No reboot
        
        Means will not stop Ec2
        
        Will not 100% synch
      - Can add extra volume during create process
    - - AMI is per region (same like snaphot)
      - specify destination region
      - can encrypt with default key
      - encrypt - > unencpty - -> not supported
        
        the rest of combination supported
    - - can't use the AMI to launch Ec2 after that
      - will still incur cost
      - existing Ec2 and snpahost will not be impacted
      - Therefore, should terminate those Ec2 or delete snapshot
      - It does not delete the EBS snapshots or the bundles in the S3 buckets and have to be removed separatel
- - - - dedicated capacity for Amazon EBS I/O.
- - - - Baseline level of CPU performance with the
      - ability to burst above the baseline for
      - workloads that don’t require sustained
      - performance