The m5.24xlarge is a general-purpose AWS EC2 instance: 96 vCPU and 384 GiB of memory, 4.00 GiB per vCPU. In the name, "m" is the general-purpose line, "5" is the generation and "24xlarge" is the size within the m5 family. It runs on Intel Xeon Platinum 8175 at 3.1 GHz, and AWS introduced it in November 2017. AWS has since shipped m6i, m7i, m8i and m9g; m6i.24xlarge is the direct replacement at this size, scoring 1,587,761 CoreMark/s against this instance's 1,374,718 — roughly 15% more throughput for the same vCPU count. No single Spot node covers 96 vCPU and 384 GiB, so the equivalent is a fleet: 6 × gp.vs1.2xlarge, 96 vCPU and 384 GiB in total, 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
m5.24xlarge gives you 96 vCPU and 384 GiB in a single machine. The largest comparable Spot node, gp.vs1.2xlarge, is 16 vCPU and 64 GiB, so the equivalent here is 6 nodes rather than one.
Spot runs as managed Kubernetes, so a 6-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 96 cores and 384 GiB in one process, it does not.
