Instances›AWS EC2›r8id›r8id.32xlarge
Compute
vCPUs128
Memory1024 GiB
Mem / vCPU8.00 GiB
ProcessorXeon Scalable
Clock speed3.9 GHz
Architecturex86_64
Storage
Type2 × 3,800 GB NVMe SSD
Bandwidth40,000 Mbps
Throughput5000 MB/s
IOPS160,000
Networking
Performance50 Gigabit
Max ENIs24
IPv6Yes
GPUNone
Family sizes
r8id.large2 vCPU · 16 GiB
r8id.xlarge4 vCPU · 32 GiB
r8id.2xlarge8 vCPU · 64 GiB
r8id.4xlarge16 vCPU · 128 GiB
r8id.8xlarge32 vCPU · 256 GiB
r8id.12xlarge48 vCPU · 384 GiB
r8id.16xlarge64 vCPU · 512 GiB
r8id.24xlarge96 vCPU · 768 GiB
r8id.32xlarge128 vCPU · 1024 GiB
r8id.48xlarge192 vCPU · 1536 GiB
r8id.metal-48xl192 vCPU · 1536 GiB
r8id.96xlarge384 vCPU · 3072 GiB
r8id.metal-96xl384 vCPU · 3072 GiB
r8id.32xlarge

r8id.32xlarge is AWS's memory-optimized EC2 size at 128 vCPU and 1024 GiB. In the name, "r" stands for RAM, "8" is the generation, "id" marks Intel processors and local NVMe storage and "32xlarge" is the size within the r8id family. It runs on Intel Xeon Scalable (Granite Rapids) at 3.9 GHz, and AWS introduced it in February 2026. AWS has since shipped r9g. The closest Spot shape is mh.vs1.2xlarge at 16 vCPU, so this instance maps to 8 of them — 128 vCPU and 1024 GiB across the fleet, $10.64/hr on AWS in US East (N. Virginia), from $0.168/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

r8id.32xlarge gives you 128 vCPU and 1,024 GiB in a single machine. The largest comparable Spot node, mh.vs1.2xlarge, is 16 vCPU and 128 GiB, so the equivalent here is 8 nodes rather than one.

Spot runs as managed Kubernetes, so a 8-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 128 cores and 1,024 GiB in one process, it does not.

No local diskr8id.32xlarge comes with 2 × 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$10.645$2.350$0.168
$10.477 savings
US Central, Chicagono AWS region$0.168
US Central, Dallasno AWS region$1.048
Hong Kong$0.168
Sydney, Australia$12.250$2.948$0.168
$12.082 savings
London, UK$12.493$2.358$1.048
$11.445 savings
US West, San Jose$0.016
US Central, Dallas 2no AWS region$1.936
When to use it
Good for
  • ●Graph and search workloads with large indexes
  • ●In-memory caches such as Redis and Memcached
  • ●Large JVM heaps and application servers that hold state
  • ●Workloads that fit inside 1024 GiB of RAM
  • ●Jobs that want 2 × 3,800 GB of local NVMe scratch space
  • ●Network-heavy services — AWS rates this size at 50 Gigabit
  • ●Anything that shards cleanly across 8 nodes, which is how it maps onto Rackspace Spot
Avoid if
  • ●The working set needs more than 1024 GiB of RAM
  • ●CPU-bound work. You are paying for memory this workload will not use.
  • ●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 128 vCPU would sit idle.
  • ●GPU or FPGA acceleration is needed
Stop overpaying AWS. This compute costs $7,770/mo on AWS vs $123/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