Instances›AWS EC2›m8idn›m8idn.24xlarge
Compute
vCPUs96
Memory384 GiB
Mem / vCPU4.00 GiB
ProcessorXeon Scalable
Clock speed3.9 GHz
Architecturex86_64
Storage
Type2 × 2,850 GB NVMe SSD
Bandwidth30,000 Mbps
Throughput3750 MB/s
IOPS120,000
Networking
Performance150 Gigabit
Max ENIs16
IPv6Yes
GPUNone
Family sizes
m8idn.large2 vCPU · 8 GiB
m8idn.xlarge4 vCPU · 16 GiB
m8idn.2xlarge8 vCPU · 32 GiB
m8idn.4xlarge16 vCPU · 64 GiB
m8idn.8xlarge32 vCPU · 128 GiB
m8idn.12xlarge48 vCPU · 192 GiB
m8idn.16xlarge64 vCPU · 256 GiB
m8idn.24xlarge96 vCPU · 384 GiB
m8idn.32xlarge128 vCPU · 512 GiB
m8idn.48xlarge192 vCPU · 768 GiB
m8idn.metal-48xl192 vCPU · 768 GiB
m8idn.96xlarge384 vCPU · 1536 GiB
m8idn.metal-96xl384 vCPU · 1536 GiB
m8idn.24xlarge

m8idn.24xlarge is AWS's general-purpose EC2 size at 96 vCPU and 384 GiB. In the name, "m" is the general-purpose line, "8" is the generation, "idn" marks Intel processors, local NVMe storage and enhanced networking and "24xlarge" is the size within the m8idn family. It runs on Intel Xeon Scalable (Granite Rapids) at 3.9 GHz, and AWS introduced it in May 2026. AWS has since shipped m9g; m9g.24xlarge is the direct replacement at this size, scoring 3,487,950 CoreMark/s against this instance's 2,315,066 — roughly 51% more throughput for the same vCPU count. The closest Spot shape is gp.vs2.2xlarge at 16 vCPU, so this instance maps to 6 of them — 96 vCPU and 384 GiB across the fleet, $9.17/hr on AWS in US East (N. Virginia), from $0.246/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

m8idn.24xlarge gives you 96 vCPU and 384 GiB in a single machine. The largest comparable Spot node, gp.vs2.2xlarge, is 16 vCPU and 64 GiB, so the equivalent here is 6 nodes rather than one.

Spot runs as managed Kubernetes, so a 6-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 96 cores and 384 GiB in one process, it does not.

No local diskm8idn.24xlarge comes with 2 × 2,850 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$9.165$3.950$0.246
$8.919 savings
US Central, Chicagono AWS region$0.246
US Central, Dallasno AWS region$0.306
Hong Kong$0.066
Sydney, Australia$0.966
London, UK$1.326
US West, San Jose$0.906
US Central, Dallas 2no AWS region$0.006
US East, N. Virginia 2$9.165$3.950$0.906
$8.259 savings
When to use it
Good for
  • ●Queue workers and scheduled jobs
  • ●Web and application servers with mixed CPU and memory demand
  • ●Microservices and container fleets
  • ●Workloads that fit inside 384 GiB of RAM
  • ●Jobs that want 2 × 2,850 GB of local NVMe scratch space
  • ●Network-heavy services — AWS rates this size at 150 Gigabit
  • ●Anything that shards cleanly across 6 nodes, which is how it maps onto Rackspace Spot
Avoid if
  • ●The working set needs more than 384 GiB of RAM
  • ●More than 4.00 GiB of RAM per vCPU is needed — that ratio is fixed for the whole family
  • ●The work is single-threaded. Most of these 96 vCPU would sit idle.
  • ●GPU or FPGA acceleration is needed
  • ●Sustained full-core CPU load. A compute-optimized family costs less per unit of work.
Stop overpaying AWS. This compute costs $6,691/mo on AWS vs $180/mo on Rackspace Spot.
  • 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