# Amazon EC2 instance types

Amazon EC2 instance types are predefined virtual machine hardware configurations that determine the compute, memory, storage, networking, and accelerator resources available to a workload.

Cloud concept. Updated 2026-10-29. Page: https://blowstack.com/tools/cloud-concepts-hub/amazon-ec2-instance-types

> An instance type represents a resource profile, allowing engineers to match a virtual machine to an application's performance and compatibility requirements. Understanding these profiles helps avoid bottlenecks, reduce unnecessary spending, and distinguish hardware selection from purchasing options such as On-Demand or Spot.

Practice exams covering Amazon EC2 instance types: [CLF-C02 AWS Certified Cloud Practitioner](https://blowstack.com/practice-exams/aws-certified-cloud-practitioner), [MLA-C02 (beta) AWS Certified Machine Learning Engineer - Associate](https://blowstack.com/practice-exams/aws-certified-machine-learning-engineer-associate), [SAA-C03 AWS Certified Solutions Architect - Associate](https://blowstack.com/practice-exams/aws-certified-solutions-architect-associate).

## 6 key aspects of Amazon EC2 instance types

Effective instance type selection combines workload profiling, hardware compatibility, sustained performance limits, storage requirements, and total cost.

1. **Workload-aligned resource profiles**: Instance families provide different balances of CPU, memory, storage, and accelerators. Select a profile based on the workload's measured limiting resource rather than assuming that more CPUs will resolve every performance problem.
2. **Family, generation, and size**: The family describes the resource emphasis, the generation identifies a hardware generation, and the size determines resource scale within that family. Compare actual specifications because size labels are not equivalent across families.
3. **Processor and software compatibility**: Processor architecture affects operating system images, application binaries, container images, and native dependencies. Validate compatibility and benchmark performance before moving between x86 and Arm configurations.
4. **Performance limits and bursting**: CPU credit behavior, network bandwidth, and block-storage throughput can limit performance independently. Distinguish sustained capacity from temporary burst capability when sizing production workloads.
5. **Storage durability boundaries**: Some configurations include local instance-store devices, while others rely on attached storage. Use local devices for data that can be recreated or replicated, and place durable state on storage designed to persist independently of the instance.
6. **Independent cost and scaling decisions**: Hardware configuration, purchasing model, and scaling strategy are separate choices. Evaluate total workload cost, including licensing, surplus CPU credits, storage, and the operational impact of resizing.

## Cloud services for Amazon EC2 instance types

EC2 supplies the hardware profiles, while EC2 Auto Scaling manages fleet size and can distribute capacity across suitable instance types. ECS and AWS Batch place containerized services or jobs onto that capacity, making workload resource requests and processor compatibility important inputs to hardware selection. Compute Optimizer adds utilization-based recommendations that help identify oversized or constrained instances. Together, these services support a feedback loop: choose compatible configurations, deploy representative workloads, observe resource use and application performance, and refine instance types or fleet size. Recommendations and scaling policies still require application-level validation because infrastructure metrics alone do not establish whether latency, reliability, or licensing requirements are satisfied.

- **[Amazon EC2](https://blowstack.com/tools/cloud-services-hub/amazon-ec2)**: EC2 exposes predefined instance types for launching virtual machines. Engineers select configurations that meet architecture, resource, storage, and networking requirements, then validate them with workload-specific measurements.
- **[Amazon EC2 Auto Scaling](https://blowstack.com/tools/cloud-services-hub/amazon-ec2-auto-scaling)**: Auto Scaling adjusts the number of instances and supports groups that use multiple instance types. Alternative types can improve capacity availability, but each must satisfy application compatibility and resource requirements.
- **[AWS Compute Optimizer](https://blowstack.com/tools/cloud-services-hub/aws-compute-optimizer)**: Compute Optimizer analyzes utilization and provides EC2 rightsizing recommendations. Memory-aware analysis requires supported memory metrics, and recommendations should be checked against application latency, licensing, and operational constraints.
- **[AWS Batch](https://blowstack.com/tools/cloud-services-hub/aws-batch)**: AWS Batch can provision EC2-backed compute environments using permitted instance types. Job requirements such as memory, vCPU count, architecture, and GPUs guide which configurations can execute the work.

## Amazon EC2 instance types exam questions

Real practice exam questions on Amazon EC2 instance types, with the correct answer and its explanation.

### Question 1 (CLF-C02)

**Question:**

A retailer runs an analytics application on Amazon EC2 that keeps a large dataset in RAM for fast queries. Monitoring shows that the application frequently runs out of memory while CPU utilization remains low. Which EC2 instance category provides the resource balance best suited to this workload?

**Correct answer:** Memory optimized

**Explanation:** Memory-optimized instances provide a high proportion of memory relative to CPU resources, making them well suited to applications that process large datasets in RAM.

### Question 2 (MLA-C02 (beta))

**Question:**

A company plans to deploy a PyTorch model on an Amazon SageMaker AI real-time endpoint. The ML engineer has identified several compatible CPU and GPU inference instance types but does not know which provides the best price-performance.

The company has representative inference payloads and a required load-test profile consisting of a gradual traffic increase followed by a sustained peak. The selected configuration must maintain p95 model latency below 100 milliseconds at the required peak request rate. The engineer must automate benchmarking of the candidate instance types with this traffic profile and compare the costs of configurations that satisfy the performance requirements. The company does not want to build or maintain a custom load-generation framework.

Which approach best meets these requirements?

**Correct answer:** Run an advanced SageMaker Inference Recommender job with the candidate instance types, representative payloads, custom traffic phases, and performance thresholds. Compare costs among configurations that meet the peak throughput and p95 latency requirements.

**Explanation:** Advanced Inference Recommender jobs support customized load tests, including candidate endpoint configurations, traffic patterns, and performance thresholds. This enables workload-specific instance comparisons without maintaining a custom load generator. Cost should be compared only among configurations that meet the required throughput and latency.

### Question 3 (SAA-C03)

**Question:**

A company runs a telemetry relay on an Amazon EC2 On-Demand Instance with 16 vCPUs and 64 GiB of memory. Measurements across complete business cycles show that the relay needs at least 4 vCPUs and 16 GiB of memory, including required headroom. The relay continuously sends 3 Gbps of data and must maintain this rate 24 hours a day.

The company wants to reduce EC2 compute costs. All candidate configurations have compatible processors and sufficient storage performance and packet-processing capacity. For configurations with burst network performance, throughput above the baseline depends on a finite network I/O credit balance.

Which configuration meets the requirements at the LOWEST compute cost?

**Correct answer:** Use a configuration with 8 vCPUs, 32 GiB of memory, and 5 Gbps baseline network bandwidth, priced at $0.28 per hour.

**Explanation:** This is the least expensive configuration that satisfies all requirements. Its baseline network bandwidth supports the continuous transfer rate without relying on burst credits, and it provides sufficient CPU and memory. Right-sizing must account for network capacity as well as CPU and memory.

## Practice Amazon EC2 instance types in a full exam

Questions on Amazon EC2 instance types in each practice exam, with every answer option and an explanation for each:

- [MLA-C02 (beta)](https://blowstack.com/practice-exams/aws-certified-machine-learning-engineer-associate): 13 questions
- [SAA-C03](https://blowstack.com/practice-exams/aws-certified-solutions-architect-associate): 13 questions
- [CLF-C02](https://blowstack.com/practice-exams/aws-certified-cloud-practitioner): 6 questions

## What is Amazon EC2 instance types

Cloud virtual machines are offered in predefined hardware configurations rather than as interchangeable units of compute. Amazon EC2 instance types express this idea through families, generations, sizes, and capability indicators. A type specifies resources such as virtual CPUs, memory, supported processor architecture, network performance, storage connectivity, and, where applicable, local storage or accelerators. Choosing an instance type is therefore an exercise in matching a workload to a resource profile, not simply choosing the largest machine within a budget.

Instance families emphasize different resource balances. General-purpose configurations suit applications with balanced CPU and memory requirements. Compute-optimized configurations suit CPU-intensive processing, while memory-optimized configurations support workloads with large in-memory working sets. Storage-optimized configurations address demanding local storage requirements, and accelerated configurations provide hardware such as GPUs for compatible applications. These categories are starting points; actual workload measurements are more useful than family labels alone.

EC2 names encode parts of the configuration. For example, m7i.large identifies the general-purpose m family, generation 7, an Intel processor variant, and the large size. Capability suffixes are family-specific, so their meanings should be checked rather than inferred universally. Sizes indicate resource scale within a family, but the same size label across different families does not guarantee equal memory, throughput, or performance. Likewise, a newer generation is not automatically the best choice for every application.

Processor compatibility matters. An Arm-based instance requires a compatible operating system image and application binaries or container images. Software compiled only for x86 cannot simply run unchanged on Arm hardware. Virtual CPU counts also require interpretation: on many x86 configurations, a vCPU represents a hardware thread, while on Graviton configurations it represents a physical core. Equal vCPU counts therefore do not guarantee equivalent application throughput.

Consider an API server with low average CPU usage and occasional traffic spikes. A burstable configuration may be economical, but sustained demand can consume CPU credits. Depending on its credit mode, the instance may fall back toward baseline performance or incur surplus credit charges. A continuously busy application may achieve more predictable economics on a non-burstable configuration. By contrast, a database that repeatedly reads from disk because its working set exceeds RAM may benefit more from additional memory than from additional CPUs.

Storage and networking impose separate limits. Attaching a faster block volume does not remove the instance's own block-storage throughput limits, and advertised network performance can include baseline and burst characteristics. Local instance-store storage must be treated as ephemeral: its data does not survive events such as instance stop or termination. Durable application state generally belongs on persistent volumes or external storage services.

Instance type selection is separate from purchasing model and scaling strategy. On-Demand, Spot, and commitment-based discounts affect cost or availability terms, not the underlying resource specification. Vertical resizing can increase resources per machine, while horizontal scaling adds machines and requires an application that can distribute work. For typical EBS-backed EC2 instances, changing type requires stopping and starting the instance, and the replacement type must satisfy compatibility requirements. Engineers should benchmark representative traffic, monitor CPU, memory, storage latency, and network utilization, and check regional availability, quotas, and capacity before adopting a configuration.

## Learn Amazon EC2 instance types in lessons

5 short lessons on Amazon EC2 instance types in 3 certification courses.

- CLF-C02: Amazon EC2 instance types: matching families to workloads (Premium), https://app.blowstack.com/lessons/amazon-ec2-instance-types-matching-families-to-workloads-clf-c02
- MLA-C02 (beta): Amazon EC2 instance types: hardware profiles for ML workloads (Premium), https://app.blowstack.com/lessons/amazon-ec2-instance-types-hardware-profiles-for-ml-workloads-mla-c02
- SAA-C03: Amazon EC2 instance types: choosing an instance family (Premium), https://app.blowstack.com/lessons/amazon-ec2-instance-types-choosing-an-instance-family-saa-c03
- SAA-C03: Amazon EC2 instance types: choosing an instance size (Premium), https://app.blowstack.com/lessons/amazon-ec2-instance-types-choosing-an-instance-size-saa-c03
- SAA-C03: CPU Architecture vs Amazon EC2 instance types (Premium), https://app.blowstack.com/lessons/cpu-architecture-vs-amazon-ec2-instance-types-saa-c03
