m5a.16xlarge is AWS's general-purpose EC2 size at 64 vCPU and 256 GiB. In the name, "m" is the general-purpose line, "5" is the generation, "a" marks AMD processors and "16xlarge" is the size within the m5a family. It runs on AMD EPYC 7571 at 2.5 GHz, and AWS introduced it in June 2019. AWS has since shipped m6a, m7a, m8a and m9g; m6a.16xlarge is the direct replacement at this size, scoring 1,416,948 CoreMark/s against this instance's 810,674 — roughly 75% more throughput for the same vCPU count. The closest Spot shape is gp.vs1.2xlarge at 16 vCPU, so this instance maps to 4 of them — 64 vCPU and 256 GiB across the fleet, about 94% 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
m5a.16xlarge gives you 64 vCPU and 256 GiB in a single machine. The largest comparable Spot node, gp.vs1.2xlarge, is 16 vCPU and 64 GiB, so the equivalent here is 4 nodes rather than one.
Spot runs as managed Kubernetes, so a 4-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 64 cores and 256 GiB in one process, it does not.
