

# Specifications for Amazon EC2 storage optimized instances
<a name="so"></a>

Storage optimized instances are designed for workloads that require high, sequential read and write access to very large data sets on local storage. They are optimized to deliver tens of thousands of low-latency, random I/O operations per second (IOPS) to applications.

For information on previous generation instance types of this category, such as I2 instances, see [Specifications for Amazon EC2 previous generation instances](pg.md).

**Topics**
+ [Instance families and instance types](#so_sizes)
+ [Instance family summary](#so_summary)
+ [Performance specifications](#so_hardware)
+ [Network specifications](#so_network)
+ [Amazon EBS specifications](#so_storage-ebs)
+ [Instance store specifications](#so_instance-store)
+ [Security specifications](#so_security)

**Pricing**  
For pricing information, see [Amazon EC2 On-Demand Pricing](https://aws.amazon.com/ec2/pricing/on-demand/).

## Instance families and instance types
<a name="so_sizes"></a>


| Instance family | Available instance types | 
| --- | --- | 
| D2 | d2.xlarge \| d2.2xlarge \| d2.4xlarge \| d2.8xlarge | 
| D3 | d3.xlarge \| d3.2xlarge \| d3.4xlarge \| d3.8xlarge | 
| D3en | d3en.xlarge \| d3en.2xlarge \| d3en.4xlarge \| d3en.6xlarge \| d3en.8xlarge \| d3en.12xlarge | 
| H1 | h1.2xlarge \| h1.4xlarge \| h1.8xlarge \| h1.16xlarge | 
| I3 | i3.large \| i3.xlarge \| i3.2xlarge \| i3.4xlarge \| i3.8xlarge \| i3.16xlarge \| i3.metal | 
| I3en | i3en.large \| i3en.xlarge \| i3en.2xlarge \| i3en.3xlarge \| i3en.6xlarge \| i3en.12xlarge \| i3en.24xlarge \| i3en.metal | 
| I4g | i4g.large \| i4g.xlarge \| i4g.2xlarge \| i4g.4xlarge \| i4g.8xlarge \| i4g.16xlarge | 
| I4i | i4i.large \| i4i.xlarge \| i4i.2xlarge \| i4i.4xlarge \| i4i.8xlarge \| i4i.12xlarge \| i4i.16xlarge \| i4i.24xlarge \| i4i.32xlarge \| i4i.metal | 
| I7i | i7i.large \| i7i.xlarge \| i7i.2xlarge \| i7i.4xlarge \| i7i.8xlarge \| i7i.12xlarge \| i7i.16xlarge \| i7i.24xlarge \| i7i.48xlarge \| i7i.metal-24xl \| i7i.metal-48xl | 
| I7ie | i7ie.large \| i7ie.xlarge \| i7ie.2xlarge \| i7ie.3xlarge \| i7ie.6xlarge \| i7ie.12xlarge \| i7ie.18xlarge \| i7ie.24xlarge \| i7ie.48xlarge \| i7ie.metal-24xl \| i7ie.metal-48xl | 
| I8g | i8g.large \| i8g.xlarge \| i8g.2xlarge \| i8g.4xlarge \| i8g.8xlarge \| i8g.12xlarge \| i8g.16xlarge \| i8g.24xlarge \| i8g.48xlarge \| i8g.metal-24xl \| i8g.metal-48xl | 
| I8ge | i8ge.large \| i8ge.xlarge \| i8ge.2xlarge \| i8ge.3xlarge \| i8ge.6xlarge \| i8ge.12xlarge \| i8ge.18xlarge \| i8ge.24xlarge \| i8ge.48xlarge \| i8ge.metal-24xl \| i8ge.metal-48xl | 
| Im4gn | im4gn.large \| im4gn.xlarge \| im4gn.2xlarge \| im4gn.4xlarge \| im4gn.8xlarge \| im4gn.16xlarge | 
| Is4gen | is4gen.medium \| is4gen.large \| is4gen.xlarge \| is4gen.2xlarge \| is4gen.4xlarge \| is4gen.8xlarge | 

## Instance family summary
<a name="so_summary"></a>


| Instance family | Hypervisor | Processor type (architecture) | Metal instances available | Dedicated Hosts support | Spot support | Hibernation support | Supported operating systems | 
| --- | --- | --- | --- | --- | --- | --- | --- | 
| D2 | Xen | Intel (x86\_64) | ✗ No | ✓ Yes | ✓ Yes | ✗ No | Windows \| Linux | 
| D3 | [Nitro v3](ec2-nitro-instances.md) | Intel (x86\_64) | ✗ No | ✗ No | ✓ Yes | ✗ No | Windows \| Linux | 
| D3en | [Nitro v3](ec2-nitro-instances.md) | Intel (x86\_64) | ✗ No | ✗ No | ✓ Yes | ✗ No | Windows \| Linux | 
| H1 | Xen | Intel (x86\_64) | ✗ No | ✓ Yes | ✓ Yes | ✗ No | Windows \| Linux | 
| I3 | Xen \* | Intel (x86\_64) | ✓ Yes | ✓ Yes | ✓ Yes | ✓ Yes | Windows \| Linux | 
| I3en | [Nitro v3](ec2-nitro-instances.md) | Intel (x86\_64) | ✓ Yes | ✓ Yes | ✓ Yes | ✓ Yes | Windows \| Linux | 
| I4g | [Nitro v4](ec2-nitro-instances.md) | AWS Graviton (arm64) | ✗ No | ✓ Yes | ✓ Yes | ✓ Yes | Linux | 
| I4i | [Nitro v4](ec2-nitro-instances.md) | Intel (x86\_64) | ✓ Yes | ✓ Yes | ✓ Yes | ✗ No | Windows \| Linux | 
| I7i | [Nitro v4](ec2-nitro-instances.md) | Intel (x86\_64) | ✓ Yes | ✓ Yes | ✓ Yes | ✓ Yes | Windows \| Linux | 
| I7ie | [Nitro v5](ec2-nitro-instances.md) | Intel (x86\_64) | ✓ Yes | ✓ Yes | ✓ Yes | ✓ Yes | Windows \| Linux | 
| I8g | [Nitro v5](ec2-nitro-instances.md) | AWS Graviton (arm64) | ✓ Yes | ✓ Yes | ✓ Yes | ✓ Yes | Linux | 
| I8ge | [Nitro v6](ec2-nitro-instances.md) | AWS Graviton (arm64) | ✓ Yes | ✓ Yes | ✓ Yes | ✓ Yes | Linux | 
| Im4gn | [Nitro v4](ec2-nitro-instances.md) | AWS Graviton (arm64) | ✗ No | ✓ Yes | ✓ Yes | ✓ Yes | Linux | 
| Is4gen | [Nitro v4](ec2-nitro-instances.md) | AWS Graviton (arm64) | ✗ No | ✗ No | ✓ Yes | ✓ Yes | Linux | 

**Note**  
\* `i3.metal` instances are built on the AWS Nitro System.

## Performance specifications
<a name="so_hardware"></a>

[See the AWS documentation website for more details](http://docs.aws.amazon.com/ec2/latest/instancetypes/so.html)

## Network specifications
<a name="so_network"></a>

[See the AWS documentation website for more details](http://docs.aws.amazon.com/ec2/latest/instancetypes/so.html)

**Note**  
1 These instances have a baseline bandwidth and can use a network I/O credit mechanism to burst beyond their baseline bandwidth on a best effort basis. Other instances types can sustain their maximum performance indefinitely. For more information, see [ instance network bandwidth](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-instance-network-bandwidth.html).  
2 These instances support enhanced networking using the Intel 82599 VF interface.

## Amazon EBS specifications
<a name="so_storage-ebs"></a>

The following table indicates which instance types are Amazon EBS optimized by default and which optionally support it. It also describes their EBS-optimized performance, including dedicated bandwidth to Amazon EBS, the typical maximum aggregate throughput that can be achieved on that dedicated connection with a streaming read workload and 128 KiB I/O size, and the maximum IOPS the instance type can support when using a 16 KiB I/O size. Instance types not listed do not support Amazon EBS optimization.

**Important**  
An instance's EBS performance is bounded by the instance's performance limits, or the aggregated performance of its attached volumes, whichever is smaller. To achieve maximum EBS performance, an instance must have attached volumes that provide a combined performance equal to or greater than the maximum instance performance. For example, to achieve `80,000` IOPS for `r6i.16xlarge`, the instance must have at least `5` `gp3` volumes provisioned with `16,000` IOPS each (`5` volumes x `16,000` IOPS = `80,000` IOPS).  
We recommend that you choose an EBS–optimized instance type that provides more dedicated Amazon EBS throughput than your application needs; otherwise, the connection between Amazon EBS and Amazon EC2 can become a performance bottleneck.

[See the AWS documentation website for more details](http://docs.aws.amazon.com/ec2/latest/instancetypes/so.html)

**Note**  
1 These instances can support maximum performance for 30 minutes at least once every 24 hours, after which they revert to their baseline performance. Other instances can sustain the maximum performance indefinitely. If your workload requires sustained maximum performance for longer than 30 minutes, use one of these instances.

## Instance store specifications
<a name="so_instance-store"></a>

The following table shows the instance store volume configuration for supported instance types, along with the aggregated IOPS performance with 4,096 byte block size at queue depth saturation. 

[See the AWS documentation website for more details](http://docs.aws.amazon.com/ec2/latest/instancetypes/so.html)

1 Volumes attached to certain instances suffer a first-write penalty unless initialized. For more information, see [Optimize disk performance for instance store volumes](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/disk-performance.html).

2 For more information, see [Instance store volume TRIM support](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ssd-instance-store.html#InstanceStoreTrimSupport).

## Security specifications
<a name="so_security"></a>

[See the AWS documentation website for more details](http://docs.aws.amazon.com/ec2/latest/instancetypes/so.html)