The m6i.32xlarge pairs 128 vCPU with 512 GiB of RAM, the 4.00 GiB-per-vCPU ratio that marks a general-purpose instance. In the name, "m" is the general-purpose line, "6" is the generation, "i" marks Intel processors and "32xlarge" is the size within the m6i family. It runs on Intel Xeon 8375C (Ice Lake) at 3.5 GHz, and AWS introduced it in August 2021. AWS has since shipped m7i, m8i and m9g; m7a.32xlarge is the direct replacement at this size, scoring 4,116,638 CoreMark/s against this instance's 2,269,001 — roughly 81% more throughput for the same vCPU count. Spot's node ladder tops out below this size, so m6i.32xlarge becomes 8 × gp.vs2.2xlarge (128 vCPU, 512 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
m6i.32xlarge gives you 128 vCPU and 512 GiB in a single machine. The largest comparable Spot node, gp.vs2.2xlarge, is 16 vCPU and 64 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 512 GiB in one process, it does not.
