AWS EC2 Instance Type

From GM-RKB
(Redirected from EC2 Instance Type)
Jump to navigation Jump to search

An AWS EC2 Instance Type is a server computer type for EC2 server instances (available in AWS EC2).



References

2024

  • (Wikipedia, 2024) ⇒ https://en.wikipedia.org/wiki/Amazon_Elastic_Compute_Cloud#Instance_types Retrieved:2024-1-14.
    • Initially, EC2 used Xen virtualization exclusively. However, on November 6, 2017, Amazon announced the new C5 family of instances that were based on a custom architecture around the KVM hypervisor, called Nitro. Each virtual machine, called an "instance", functions as a virtual private server. Amazon sizes instances based on "Elastic Compute Units". The performance of otherwise identical virtual machines may vary. [1] On November 28, 2017, AWS announced a bare-metal instance type offering marking a remarkable departure from exclusively offering virtualized instance types.
    • As of January 2019, the following instance types were offered:
      • General Purpose: A1, T3, T2, M5, M5a, M4, T3a
      • Compute Optimized: C5, C5n, C4
      • Memory Optimized: R5, R5a, R4, X1e, X1, High Memory, z1d
      • Accelerated Computing: P3, P2, G3, F1
      • Storage Optimized: H1, I3, D2
    • the following payment methods by instance were offered:
      • On-demand: pay by the hour without commitment.
      • Reserved: rent instances with one-time payment receiving discounts on the hourly charge.
      • Spot: bid-based service: runs the jobs only if the spot price is below the bid specified by bidder. The spot price is claimed to be supply-demand based, however a 2011 study concluded that the price was generally not set to clear the market, but was dominated by an undisclosed reserve price.[2] [3]

2020


  1. J. Dejun, G. Pierre and C.-H. Chi. EC2 Performance Analysis for Resource Provisioning of Service-Oriented Applications. In Proceedings of the Workshop on Non-Functional Properties and SLA Management in Service-Oriented Computing, November 2009.
  2. Cite error: Invalid <ref> tag; no text was provided for refs named Ben-Yehuda Ben-Yehuda Schuster Tsafrir 2011
  3. Cite error: Invalid <ref> tag; no text was provided for refs named Wu-et-al