Instance Family

This term is happend in Amazon EC2 service.

EC2 instance don’t just come in different types. Each type comes in different sizes, with different allotments of vCPUs and memory. Choosing the right size is critical to using your instances efficiently.

An instance’s full type consists of its family name, followed by the generation number, and then the size. So an m5.xlarge is an m-type instance from the 5th generation of m-type instances, in the extra-large size deployment.

  • T instances - General purpose instances with burstable performance.

Use cases: websites, web app, built servers, code repos, microservices, test, staging, dev env, business apps

  • M instances - General purpose instances

Use cases: Small and mid size db, data processing tasks that require additional memory, caching fleets, backend SAP servers, Microsoft Sharepoint, cluster computing, other enterprise apps

  • C instances - Compute-optimized instances

Use cases: High performance web servers, high performance computing, scientific modeling, batch processing, distributed analytics, maching / deep learning inference, ad serving, highly scalable multiplayer gaming, video encoding.

  • X instances - extremely large amounts (up to almost 4TB) of high-performance memory

Use cases: In-memory databases (SAP HANA), big data processing engines (Apache Spark or Presto)

  • R instances - high performance memory

Use cases: High performance DB, data mining and analytics, in-memory db, distributed web scale in-memory caches, application performing real-time processing of unstructured big data, Hadoop/Spark clusters, and other enterprise data apps.

  • P instances - General-purpose GPU compute instances

Use cases: machine learning, deep learning, high performance computing, computational fluid dyanmics, computational finance, seismic analytics, speech recognition, automomous vehicles, pharmaceutical discovery

  • F instances - Instances with customize-able hardware acceleration with field programmable gate arrays (FPGAs)

Use cases: Genomics research, financial analytics, real-time video processing, big data search and analysis, and security analytics

  • H instances - High disk thruput

Use cases: Amazon EMR-based workloads, distributed file system such as HDFS and MapR-FS, network file systems, log or data processing applications such as Apache Kafka, big data workload clusters.

  • I instances - Instances backed with Non-Volatile Memory Express (NVMe) SSDs, optmized for low latency, very high random I/O performance, and high sequential real thruput.

Use cases: NoSQL DB, in-memory db (eg: Aerospke), scale out transactional db, data warehousing, Elasticsearch, and analytics workloads

  • D Instances - Lowest price per disk thruput performance on Amazon EC2. Instances are backed by HDD-based local storage

Use cases: Massively parallel processing (MPP) data warehousing, MapReduce and Hadoop distributed computing, distributed file systems, network file systems, log or data processing apps

  • G Instances - instances optmized for graphics intensive apps

Use cases: 3D visualizations, graphics intensive remote workstations, 3D rendering, application streaming, video encoding, other server side graphics workloads