Instances›AWS EC2›m8idb›m8idb.metal-48xl
Compute
vCPUs192
Memory768 GiB
Mem / vCPU4.00 GiB
ProcessorXeon Scalable
Clock speed3.9 GHz
Architecturex86_64
Storage
Type3 × 3,800 GB NVMe SSD
Bandwidth150,000 Mbps
Throughput18750 MB/s
IOPS720,000
Networking
Performance200 Gigabit
Max ENIs24
IPv6Yes
GPUNone
Family sizes
m8idb.large2 vCPU · 8 GiB
m8idb.xlarge4 vCPU · 16 GiB
m8idb.2xlarge8 vCPU · 32 GiB
m8idb.4xlarge16 vCPU · 64 GiB
m8idb.8xlarge32 vCPU · 128 GiB
m8idb.12xlarge48 vCPU · 192 GiB
m8idb.16xlarge64 vCPU · 256 GiB
m8idb.24xlarge96 vCPU · 384 GiB
m8idb.32xlarge128 vCPU · 512 GiB
m8idb.48xlarge192 vCPU · 768 GiB
m8idb.metal-48xl192 vCPU · 768 GiB
m8idb.96xlarge384 vCPU · 1536 GiB
m8idb.metal-96xl384 vCPU · 1536 GiB
m8idb.metal-48xl

The m8idb.metal-48xl is a general-purpose AWS EC2 instance: 192 vCPU and 768 GiB of memory, 4.00 GiB per vCPU. In the name, "m" is the general-purpose line, "8" is the generation, "idb" marks Intel processors, local NVMe storage and block-storage optimisation and "metal-48xl" is the size within the m8idb family. It runs on Intel Xeon Scalable (Granite Rapids) at 3.9 GHz, and AWS introduced it in June 2026. AWS has since shipped m9g; m9g.metal-48xl is the direct replacement at this size. No single Spot node covers 192 vCPU and 768 GiB, so the equivalent is a fleet: 12 × gp.vs2.2xlarge, 192 vCPU and 768 GiB in total, $18.33/hr on AWS in US East (N. Virginia), from $0.492/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

m8idb.metal-48xl gives you 192 vCPU and 768 GiB in a single machine. The largest comparable Spot node, gp.vs2.2xlarge, is 16 vCPU and 64 GiB, so the equivalent here is 12 nodes rather than one.

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

No local diskm8idb.metal-48xl comes with 3 × 3,800 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$18.330$6.527$0.492
$17.838 savings
US Central, Chicagono AWS region$0.492
US Central, Dallasno AWS region$0.612
Hong Kong$0.132
Sydney, Australia$1.932
London, UK$2.652
US West, San Jose$1.812
US Central, Dallas 2no AWS region$0.012
US East, N. Virginia 2$18.330$6.527$1.812
$16.518 savings
When to use it
Good for
  • ●Development, staging and CI environments
  • ●Small to mid-size relational databases
  • ●Backend services with no single dominant resource
  • ●Workloads that fit inside 768 GiB of RAM
  • ●Jobs that want 3 × 3,800 GB of local NVMe scratch space
  • ●Network-heavy services — AWS rates this size at 200 Gigabit
  • ●Anything that shards cleanly across 12 nodes, which is how it maps onto Rackspace Spot
Avoid if
  • ●The working set needs more than 768 GiB of RAM
  • ●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
  • ●The work is single-threaded. Most of these 192 vCPU would sit idle.
  • ●GPU or FPGA acceleration is needed
$13,381/mo on AWS on-demand against $359/mo on Rackspace Spot for the 12-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