Please enable JavaScript.

Coggle requires JavaScript to display documents.

Ec2-Note (type (Spot instance (defintion (2 minute notice before terminate…

- - - - steady state/predictable usage
      - want to reserved for long period such as 1 to 3 years
      - For regulatory requirement that not support for multi tenant requirement
      - Demo Monthly calculator show all upfrant, partial upfront, pricing
    - - standard RI
        
        Can;t chnge within same family
        
        provide most discount of on-demand
      - Convertible RI
        
        different config nstance family, operating system, and tenancy
        
        can convert as long as ithe price is EQUAL or Greater
        
        EX: can change from T2 to M4
      - schedule RI
        
        Used case: let see weekly sale or monthly sale
        
        predictable, recurring schedule that require on fraction of daily, weekly or monthly
    - - 1, All upfront - will enjoy max discount
        
        partial upfront -lesser discount
  - - - ex: Vmware, mcirosft SQL
  - - - New applicaton to be tested
      - App with short term or spiky
  - - - that have fltextexible start/end time
      - SUPPLEMENT On-Demand Instances, where appropriate, and are not meant to handle 100% of your workload.
      - They are not a good choice for sensitive workloads or databases.
      - 2 minute notice before terminate
        
        solution
        
        User spot block to reserver 1 to 6 hours
    - - Used case: {Pharmaceutical/chemical companies that do do huge computing at 4 am that will provide saving rather do that office hour
    - - In EMR (elastic Map Reduce )have an non-spot,instance be the "Master" node a
        
        nd then use Spot Fleets as your core & task nodes; essentially giving you tremendous compute power for a fraction of the cost in comparison to say using regular on-demand instances, and
        
        if the Spot instances get terminated - it's no problem, the tasks will just be redistributed to another Spot instance as and when they are provisioned.
      - However, you can use all Spot Instances for any stateless, non-production application, such as development and test servers, where occasional downtime is acceptable.
      - Various fault-tolerant and flexible applications. Examples include web servers, API backends, continuous integration/continuous development, and Hadoop data processing (gig data)
      - Workloads that constantly save data to persistent storage—including Amazon Simple Storage Service (Amazon S3), Amazon Elastic Block Store (Amazon EBS), Amazon Elastic File System (Amazon EFS), Amazon DynamoDB, or Amazon Relational Database Service (Amazon RDS)—can work effectively with Spot Instances.
    - - spot price
        
        Current price of Ec2
      - spot instance request
        
        the bidding price that you willing to pay
      - if your spot instance request is 1 dollar & the spot price is <1 or =1 then the spot instance assign to you
    - - the contents from the instance memory (RAM) to your Amazon EBS root volume.
      - limitation
        
        AMI used to launch the instance must be encrypted,
        
        not all instance type support
        
        Must have 122GB in EBS
      - Perfromance to resume depend on size of the EBS and the file
  - - - 5 physical server
        
        Shared tenant
        
        2 servers . Ec2 with other customer. Ec2 start/stop move to other server
        
        dedicated instance
        
        2 server(hypervisor), Ec2 start stop move to other server
        
        dedicated host
        
        1 server
        
        start/stop Ec2 remain
- - - - 1.Charges not incur for Ec2.
      - While the instance is stopped, you can treat its root volume like any other volume, and modify it for e.g. repair file system problems or update software or change the instance type, user data, EBS otpmization attributes etc
      - EBS Volume can be detached from the stopped instance, and attached to a running instance, modified, detached from the running instance, and then reattached to the stopped instance.
      - It should be reattached using the storage device name that’s specified as the root device in the block device mapping for the instance.
      - 2.Charges are only incurred for the EBS storage and not for the2. instance hourly charge or data transfer.
      - Charges for full hour are incurred for every transition from stopped to running, even if the transition is within the same hour for e
      - .g. if you stop and start your instances 2 times in an hour, you would be charged for 3 full hours, one for the start and then for the 2 transitions as if you had 3 instances running during that hour
  - - - Both EBS-backed and Instance store-backed instances can be rebooted
      - An instance retains it public DNS, public and private IP address during the reboot(2 Pub and 1 priv)
      - Data on the EBS and Instance store volume is also retained
      - Amazon recommends to use Amazon EC2 to reboot the instance instead of running the operating system reboot command from your instance as it performs a hard reboot if the instance does not cleanly shutdown within four minutes also creates an API record in CloudTrail, if enabled.
      - reboot will not cause instance store back to delete its content
- - - - Public key maintain by AWS
    - - private key to maintain by u
      - download the access key and secret key
- - - - A block device is a storage device that moves data in sequences of bytes or bits (blocks). T
      - hese devices support random access and generally use buffered I/O. :
      - Examples include hard disks, CD-ROM drives, and flash drives. A block device can be physically attached to a computer or accessed remotely as if it were physically attached to the computer. Amazon EC2 supports two types of block devices
    - - EBS volumes (remote storage devices)
      - Instance store volumes (virtual devices whose underlying hardware is physically attached to the host computer for the instance)
    - - A block device mapping defines the block devices (instance store volumes and EBS volumes) to attach to an instance. Y
      - ou can specify a block device mapping as part of creating an AMI so that the mapping is used by all instances launched from the AMI.
      - Alternatively, you can specify a block device mapping when you launch an instance, so this mapping overrides the one specified in the AMI from which you launched the instance