- 1. On-Demand
- a. Pricing Model: Standard Retail
- b. Attributes
- i. Default type
- ii. Most expensive
- iii. No commitment and no advanced fee
- iv. Billed on an hourly basis
- 2. Reserved Instances
- a. Pricing Model: Pre-paid
- b. Attributes
- i. Less expensive
- ii. Requires a commitment (1 or 3 year commitment)
- iii. Reserved capacity. AWS will never over-provision
- iv. Lower hourly rate
- v. RI can be sold on the AWS marketplace
- vi. Commiting to utilization
- c. Purchase with following factors:
- i. Platform (OS installed)
- ii. Instance Type (size of the instance)
- iii. Availability Zone
- iv. Term (1 or 3 years)
- v. Tenancy (Hardware / Dedicated)
- vi. Offering (different payment plan)
- d. When creating a new instance you can apply the Reserved instance credit
- 3. Spot Instances
- a. Pricing Model: Disposable machines that you bid on, if somebody outbids you then you lose it
- b. Attributes
- i. Unused capacity
- ii. Very cheap hourly rate
- iii. Not garaunteed
- iv. Based on a bid
- v. Ideal for raw processing power, grid-like applications
- vi. Highly scriptable
- c. Request Process
- i. Max bid
- ii. Set a launch group so that all your instances launch at the same time
- iii. Presistent request, perpetual request…as long as the cost is below a certain threshold you will grab those instances
- iv. Key pair needs to be specified
- v. When the request is fulfilled then you can go grab those instances
- vi. If you are outbid, you will get dropped…
- 4. EC2 Instance Family
- a. Micro Instances
- i. Lowest end
- ii. Family Codes: T
- b. General Purpose
- i. Family Codes: T & M
- c. Compute optimized
- i. Family Codes: C
- d. GPU instances
- i. Family Codes: G
- e. Memory optimized
- i. Family Codes: R
- f. Storage optimized
- i. Family Codes: I & D
- a. Micro Instances
Advertisements
Pingback: AWS Certified SysOps Administrator Exam: Study Guide | Sky Cliffs