Instances›AWS EC2›c8i›c8i.8xlarge
Compute
vCPUs32
Memory64 GiB
Mem / vCPU2.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
c8i.large2 vCPU · 4 GiB
c8i.xlarge4 vCPU · 8 GiB
c8i.2xlarge8 vCPU · 16 GiB
c8i.4xlarge16 vCPU · 32 GiB
c8i.8xlarge32 vCPU · 64 GiB
c8i.12xlarge48 vCPU · 96 GiB
c8i.16xlarge64 vCPU · 128 GiB
c8i.24xlarge96 vCPU · 192 GiB
c8i.32xlarge128 vCPU · 256 GiB
c8i.48xlarge192 vCPU · 384 GiB
c8i.metal-48xl192 vCPU · 384 GiB
c8i.96xlarge384 vCPU · 768 GiB
c8i.metal-96xl384 vCPU · 768 GiB
c8i.8xlarge

The c8i.8xlarge pairs 32 vCPU with 64 GiB of RAM, the 2.00 GiB-per-vCPU ratio that marks a compute-optimized instance. In the name, "c" stands for compute, "8" is the generation, "i" marks Intel processors and "8xlarge" is the size within the c8i family. It runs on Intel Xeon Scalable (Granite Rapids) at 3.9 GHz, and AWS introduced it in October 2025. AWS has since shipped c9g; c9g.8xlarge is the direct replacement at this size, scoring 1,163,636 CoreMark/s against this instance's 761,814 — roughly 53% more throughput for the same vCPU count. Spot's node ladder tops out below this size, so c8i.8xlarge becomes 2 × ch.vs1.2xlarge (32 vCPU, 64 GiB combined), 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

c8i.8xlarge gives you 32 vCPU and 64 GiB in a single machine. The largest comparable Spot node, ch.vs1.2xlarge, is 16 vCPU and 32 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 64 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.499$0.631$0.082
$1.417 savings
US Central, Chicagono AWS region$0.022
US Central, Dallasno AWS region$0.222
Hong Kong$0.082
Sydney, Australia$1.958$0.813$0.082
$1.876 savings
London, UK$1.782$0.508$0.262
$1.520 savings
US West, San Jose$1.870$0.627$0.004
$1.866 savings
US Central, Dallas 2no AWS region$0.244
US East, N. Virginia 2$1.499$0.631$0.324
$1.175 savings
When to use it
Good for
  • ●High-traffic web and API serving
  • ●Scientific modelling and simulation
  • ●Ad serving and real-time bidding
  • ●Workloads that fit inside 64 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 64 GiB of RAM
  • ●More than 2.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
  • ●Memory-hungry applications. A memory-optimized family gives more RAM per dollar.
$1,095/mo on AWS on-demand against $60/mo on Rackspace Spot for the 2-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