Instances›AWS EC2›i3en›i3en.6xlarge
Compute
vCPUs24
Memory192 GiB
Mem / vCPU8.00 GiB
ProcessorXeon Platinum 8175
Clock speed3.1 GHz
Architecturex86_64
Storage
Type2 × 7,500 GB NVMe SSD
Bandwidth4,750 Mbps
Throughput593.75 MB/s
IOPS20,000
Networking
Performance25 Gigabit
Max ENIs8
IPv6Yes
GPUNone
Family sizes
i3en.large2 vCPU · 16 GiB
i3en.xlarge4 vCPU · 32 GiB
i3en.2xlarge8 vCPU · 64 GiB
i3en.3xlarge12 vCPU · 96 GiB
i3en.6xlarge24 vCPU · 192 GiB
i3en.12xlarge48 vCPU · 384 GiB
i3en.24xlarge96 vCPU · 768 GiB
i3en.metal96 vCPU · 768 GiB
i3en.6xlarge

i3en.6xlarge is AWS's storage-optimized EC2 size at 24 vCPU and 192 GiB. In the name, "i" is I/O, meaning local storage, "3" is the generation, "en" marks extended capacity and enhanced networking and "6xlarge" is the size within the i3en family. It runs on Intel Xeon Platinum 8175 at 3.1 GHz, and AWS introduced it in May 2019. AWS has since shipped i4i, i7i and i8g; i7ie.6xlarge is the direct replacement at this size, scoring 646,726 CoreMark/s against this instance's 355,626 — roughly 82% more throughput for the same vCPU count. The closest Spot shape is mh.vs1.2xlarge at 16 vCPU, so this instance maps to 2 of them — 32 vCPU and 256 GiB across the fleet, $2.71/hr on AWS in US East (N. Virginia), from $0.042/hr on Rackspace Spot. Spot delivers compute as managed Kubernetes, so a node pool of that size is the native shape of the answer rather than a workaround — provided the workload scales horizontally.

Match qualityScale-out match

i3en.6xlarge gives you 24 vCPU and 192 GiB in a single machine. The largest comparable Spot node, mh.vs1.2xlarge, is 16 vCPU and 128 GiB, so the equivalent here is 2 nodes rather than one.

Spot runs as managed Kubernetes, so a 2-node pool is the normal way to run things rather than a workaround. If your workload already sits behind a load balancer, a queue or a scheduler, it spreads across them without changes. If it needs all 24 cores and 192 GiB in one process, it does not.

No local diski3en.6xlarge comes with 2 × 7,500 GB NVMe SSD attached to the machine. Spot nodes use network storage only, so that disk doesn't come with it. If you were using it as fast scratch space, you'd move to a persistent volume or object storage, which are slower to read.
Pricing by region
1 hr
RegionAWS on-demandAWS Spot1-yr Reserved3-yr ReservedRackspace SpotYou save
US East, N. Virginia$2.712$1.009$1.847$1.180$0.042
$2.670 savings
US Central, Chicagono AWS region$0.042
US Central, Dallasno AWS region$0.262
Hong Kong$3.580$2.448$1.558$0.042
$3.538 savings
Sydney, Australia$3.252$0.584$2.224$1.416$0.042
$3.210 savings
London, UK$3.156$0.408$2.158$1.372$0.262
$2.894 savings
US West, San Jose$3.000$0.326$2.049$1.304$0.003
$2.997 savings
US Central, Dallas 2no AWS region$0.363
When to use it
Good for
  • ●Transactional databases with heavy random I/O
  • ●Streaming ingest that spools to local disk
  • ●Elasticsearch and OpenSearch data nodes
  • ●Workloads that fit inside 192 GiB of RAM
  • ●Jobs that want 2 × 7,500 GB of local NVMe scratch space
  • ●Network-heavy services — AWS rates this size at 25 Gigabit
  • ●Anything that shards cleanly across 2 nodes, which is how it maps onto Rackspace Spot
Avoid if
  • ●Starting a new deployment. i7ie.6xlarge is the newer generation at this size.
  • ●The working set needs more than 192 GiB of RAM
  • ●GPU or FPGA acceleration is needed
  • ●Workloads that never touch local disk. The instance-store premium is wasted.
  • ●More than 8.00 GiB of RAM per vCPU is needed — that ratio is fixed for the whole family
  • ●The work is single-threaded. Most of these 24 vCPU would sit idle.
$1,980/mo on AWS on-demand against $31/mo on Rackspace Spot for the 2-node equivalent — market-priced, not list-priced.
  • Spot sells spare capacity at market prices. It is the cheapest compute on the internet.
  • Prices are set by supply and demand. You pay what the market decides.
  • Compute is delivered as fully managed Kubernetes. All infrastructure is taken care of.
  • Egress costs $0.01/GB after the free allowance. AWS charges $0.09/GB.
Build your Cloudspace
Frequently asked questions