Instances›AWS EC2›c8id›c8id.48xlarge
Compute
vCPUs192
Memory384 GiB
Mem / vCPU2.00 GiB
ProcessorXeon Scalable
Clock speed3.9 GHz
Architecturex86_64
Storage
Type3 × 3,800 GB NVMe SSD
Bandwidth60,000 Mbps
Throughput7500 MB/s
IOPS240,000
Networking
Performance75 Gigabit
Max ENIs24
IPv6Yes
GPUNone
Family sizes
c8id.large2 vCPU · 4 GiB
c8id.xlarge4 vCPU · 8 GiB
c8id.2xlarge8 vCPU · 16 GiB
c8id.4xlarge16 vCPU · 32 GiB
c8id.8xlarge32 vCPU · 64 GiB
c8id.12xlarge48 vCPU · 96 GiB
c8id.16xlarge64 vCPU · 128 GiB
c8id.24xlarge96 vCPU · 192 GiB
c8id.32xlarge128 vCPU · 256 GiB
c8id.48xlarge192 vCPU · 384 GiB
c8id.metal-48xl192 vCPU · 384 GiB
c8id.96xlarge384 vCPU · 768 GiB
c8id.metal-96xl384 vCPU · 768 GiB
c8id.48xlarge

The c8id.48xlarge pairs 192 vCPU with 384 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, "id" marks Intel processors and local NVMe storage and "48xlarge" is the size within the c8id family. It runs on Intel Xeon Scalable (Granite Rapids) at 3.9 GHz, and AWS introduced it in February 2026. AWS has since shipped c9g; c9g.48xlarge is the direct replacement at this size. Spot's node ladder tops out below this size, so c8id.48xlarge becomes 12 × ch.vs1.2xlarge (192 vCPU, 384 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

c8id.48xlarge gives you 192 vCPU and 384 GiB in a single machine. The largest comparable Spot node, ch.vs1.2xlarge, is 16 vCPU and 32 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 384 GiB in one process, it does not.

No local diskc8id.48xlarge 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$10.645$2.086$0.492
$10.152 savings
US Central, Chicagono AWS region$0.132
US Central, Dallasno AWS region$1.332
Hong Kong$0.492
Sydney, Australia$13.971$2.296$0.492
$13.479 savings
London, UK$1.572
US West, San Jose$0.024
US Central, Dallas 2no AWS region$1.464
US East, N. Virginia 2$10.645$2.086$1.944
$8.701 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 384 GiB of RAM
  • ●Jobs that want 3 × 3,800 GB of local NVMe scratch space
  • ●Network-heavy services — AWS rates this size at 75 Gigabit
  • ●Anything that shards cleanly across 12 nodes, which is how it maps onto Rackspace Spot
Avoid if
  • ●The working set needs more than 384 GiB of RAM
  • ●GPU or FPGA acceleration is needed
  • ●Memory-hungry applications. A memory-optimized family gives more RAM per dollar.
  • ●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 192 vCPU would sit idle.
Stop overpaying AWS. This compute costs $7,770/mo on AWS vs $359/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