Instances›AWS EC2›m9g›m9g.8xlarge
Compute
vCPUs32
Memory128 GiB
Mem / vCPU4.00 GiB
ProcessorGraviton5 Processor
Clock speed3.3 GHz
Architecturearm64
Storage
TypeEBS only
Bandwidth12,000 Mbps
Throughput1500 MB/s
IOPS48,000
Networking
Performance17 Gigabit
Max ENIs10
IPv6Yes
GPUNone
Family sizes
m9g.medium1 vCPU · 4 GiB
m9g.large2 vCPU · 8 GiB
m9g.xlarge4 vCPU · 16 GiB
m9g.2xlarge8 vCPU · 32 GiB
m9g.4xlarge16 vCPU · 64 GiB
m9g.8xlarge32 vCPU · 128 GiB
m9g.12xlarge48 vCPU · 192 GiB
m9g.16xlarge64 vCPU · 256 GiB
m9g.24xlarge96 vCPU · 384 GiB
m9g.48xlarge192 vCPU · 768 GiB
m9g.metal-48xl192 vCPU · 768 GiB
m9g.8xlarge

m9g.8xlarge is AWS's general-purpose EC2 size at 32 vCPU and 128 GiB. In the name, "m" is the general-purpose line, "9" is the generation, "g" marks AWS Graviton (ARM) processors and "8xlarge" is the size within the m9g family. It runs on AWS Graviton5 Processor at 3.3 GHz, and AWS introduced it in June 2026. m9g is the current generation of the m family, so there is no newer AWS size to migrate to. 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

m9g.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.

x86_64 onlym9g.8xlarge is Graviton (arm64) and Rackspace Spot has no arm64 nodes, so you'd be moving to x86. You'll need x86 builds of your images, and per-core speed differs between the chips — worth testing before you decide how many nodes to run.
Pricing by region
1 hr
RegionAWS on-demandAWS Spot1-yr Reserved3-yr ReservedRackspace SpotYou save
US East, N. Virginia$1.565$0.473$0.082
$1.483 savings
US Central, Chicagono AWS region$0.082
US Central, Dallasno AWS region$0.102
Hong Kong$0.022
Sydney, Australia$1.957$0.708$0.322
$1.635 savings
London, UK$0.442
US West, San Jose$0.302
US Central, Dallas 2no AWS region$0.002
US East, N. Virginia 2$1.565$0.473$0.302
$1.263 savings
When to use it
Good for
  • ●Backend services with no single dominant resource
  • ●Queue workers and scheduled jobs
  • ●Web and application servers with mixed CPU and memory demand
  • ●Workloads that fit inside 128 GiB of RAM
  • ●Parallel work that can occupy 32 vCPU
  • ●Network-heavy services — AWS rates this size at 17 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
  • ●You cannot rebuild x86-only binaries or vendor images for aarch64
  • ●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 32 vCPU would sit idle.
  • ●Local NVMe or instance-store disk is a hard requirement
  • ●GPU or FPGA acceleration is needed
m9g.8xlarge runs $1,143/mo on AWS on-demand. The 2-node equivalent on Rackspace Spot: $60/mo.
  • 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