Instances›AWS EC2›m8i›m8i.8xlarge
Compute
vCPUs32
Memory128 GiB
Mem / vCPU4.00 GiB
ProcessorXeon Scalable
Clock speed3.9 GHz
Architecturex86_64
Storage
TypeEBS only
Bandwidth10,000 Mbps
Throughput1250 MB/s
IOPS40,000
Networking
Performance15 Gigabit
Max ENIs10
IPv6Yes
GPUNone
Family sizes
m8i.large2 vCPU · 8 GiB
m8i.xlarge4 vCPU · 16 GiB
m8i.2xlarge8 vCPU · 32 GiB
m8i.4xlarge16 vCPU · 64 GiB
m8i.8xlarge32 vCPU · 128 GiB
m8i.12xlarge48 vCPU · 192 GiB
m8i.16xlarge64 vCPU · 256 GiB
m8i.24xlarge96 vCPU · 384 GiB
m8i.32xlarge128 vCPU · 512 GiB
m8i.48xlarge192 vCPU · 768 GiB
m8i.metal-48xl192 vCPU · 768 GiB
m8i.96xlarge384 vCPU · 1536 GiB
m8i.metal-96xl384 vCPU · 1536 GiB
m8i.8xlarge

m8i.8xlarge is AWS's general-purpose EC2 size at 32 vCPU and 128 GiB. In the name, "m" is the general-purpose line, "8" is the generation, "i" marks Intel processors and "8xlarge" is the size within the m8i family. It runs on Intel Xeon Scalable (Granite Rapids) at 3.9 GHz, and AWS introduced it in August 2025. AWS has since shipped m9g; m9g.8xlarge is the direct replacement at this size, scoring 1,176,038 CoreMark/s against this instance's 765,154 — roughly 54% more throughput for the same vCPU count. The closest Spot shape is gp.vs2.2xlarge at 16 vCPU, so this instance maps to 2 of them — 32 vCPU and 128 GiB across the fleet, about 95% below the US East (N. Virginia) on-demand rate. 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

m8i.8xlarge gives you 32 vCPU and 128 GiB in a single machine. The largest comparable Spot node, gp.vs2.2xlarge, is 16 vCPU and 64 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 32 cores and 128 GiB in one process, it does not.

Pricing by region
1 hr
RegionAWS on-demandAWS Spot1-yr Reserved3-yr ReservedRackspace SpotYou save
US East, N. Virginia$1.693$0.553$0.082
$1.611 savings
US Central, Chicagono AWS region$0.082
US Central, Dallasno AWS region$0.102
Hong Kong$0.022
Sydney, Australia$2.117$0.968$0.322
$1.795 savings
London, UK$1.958$0.647$0.442
$1.516 savings
US West, San Jose$1.976$0.873$0.302
$1.674 savings
US Central, Dallas 2no AWS region$0.002
US East, N. Virginia 2$1.693$0.553$0.302
$1.391 savings
When to use it
Good for
  • ●Microservices and container fleets
  • ●Development, staging and CI environments
  • ●Small to mid-size relational databases
  • ●Workloads that fit inside 128 GiB of RAM
  • ●Parallel work that can occupy 32 vCPU
  • ●Network-heavy services — AWS rates this size at 15 Gigabit
  • ●Anything that shards cleanly across 2 nodes, which is how it maps onto Rackspace Spot
Avoid if
  • ●The working set needs more than 128 GiB of RAM
  • ●The work is single-threaded. Most of these 32 vCPU would sit idle.
  • ●Local NVMe or instance-store disk is a hard requirement
  • ●GPU or FPGA acceleration is needed
  • ●Sustained full-core CPU load. A compute-optimized family costs less per unit of work.
  • ●More than 4.00 GiB of RAM per vCPU is needed — that ratio is fixed for the whole family
Stop overpaying AWS. This compute costs $1,236/mo on AWS vs $60/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