The c6in.32xlarge pairs 128 vCPU with 256 GiB of RAM, the 2.00 GiB-per-vCPU ratio that marks a compute-optimized instance. In the name, "c" stands for compute, "6" is the generation, "in" marks Intel processors and enhanced networking and "32xlarge" is the size within the c6in family. It runs on Intel Xeon 8375C (Ice Lake) at 3.5 GHz, and AWS introduced it in November 2022. AWS has since shipped c7i, c8in and c9g; c7a.32xlarge is the direct replacement at this size, scoring 4,052,343 CoreMark/s against this instance's 2,142,887 — roughly 89% more throughput for the same vCPU count. Spot's node ladder tops out below this size, so c6in.32xlarge becomes 8 × ch.vs1.2xlarge (128 vCPU, 256 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
c6in.32xlarge gives you 128 vCPU and 256 GiB in a single machine. The largest comparable Spot node, ch.vs1.2xlarge, is 16 vCPU and 32 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 256 GiB in one process, it does not.
