Instances›AWS EC2›m6a›m6a.12xlarge
Compute
vCPUs48
Memory192 GiB
Mem / vCPU4.00 GiB
ProcessorEPYC 7R13 Processor
Clock speed3.6 GHz
Architecturex86_64
Storage
TypeEBS only
Bandwidth15,000 Mbps
Throughput1875 MB/s
IOPS60,000
Networking
Performance18.75 Gigabit
Max ENIs8
IPv6Yes
GPUNone
Family sizes
m6a.large2 vCPU · 8 GiB
m6a.xlarge4 vCPU · 16 GiB
m6a.2xlarge8 vCPU · 32 GiB
m6a.4xlarge16 vCPU · 64 GiB
m6a.8xlarge32 vCPU · 128 GiB
m6a.12xlarge48 vCPU · 192 GiB
m6a.16xlarge64 vCPU · 256 GiB
m6a.24xlarge96 vCPU · 384 GiB
m6a.32xlarge128 vCPU · 512 GiB
m6a.48xlarge192 vCPU · 768 GiB
m6a.metal192 vCPU · 768 GiB
m6a.12xlarge

The m6a.12xlarge is a general-purpose AWS EC2 instance: 48 vCPU and 192 GiB of memory, 4.00 GiB per vCPU. In the name, "m" is the general-purpose line, "6" is the generation, "a" marks AMD processors and "12xlarge" is the size within the m6a family. It runs on AMD EPYC 7R13 Processor at 3.6 GHz, and AWS introduced it in November 2021. AWS has since shipped m7a, m8a and m9g; m7a.12xlarge is the direct replacement at this size, scoring 1,543,408 CoreMark/s against this instance's 1,009,411 — roughly 53% more throughput for the same vCPU count. No single Spot node covers 48 vCPU and 192 GiB, so the equivalent is a fleet: 3 × gp.vs2.2xlarge, 48 vCPU and 192 GiB in total, 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

m6a.12xlarge gives you 48 vCPU and 192 GiB in a single machine. The largest comparable Spot node, gp.vs2.2xlarge, is 16 vCPU and 64 GiB, so the equivalent here is 3 nodes rather than one.

Spot runs as managed Kubernetes, so a 3-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 48 cores and 192 GiB in one process, it does not.

Pricing by region
1 hr
RegionAWS on-demandAWS Spot1-yr Reserved3-yr ReservedRackspace SpotYou save
US East, N. Virginia$2.074$0.760$1.372$0.941$0.123
$1.951 savings
US Central, Chicagono AWS region$0.123
US Central, Dallasno AWS region$0.153
Hong Kong$0.033
Sydney, Australia$2.592$1.252$1.715$1.176$0.483
$2.109 savings
London, UK$2.398$0.813$1.584$1.090$0.663
$1.735 savings
US West, San Jose$2.419$0.661$1.595$1.102$0.453
$1.966 savings
US Central, Dallas 2no AWS region$0.003
US East, N. Virginia 2$2.074$0.760$1.372$0.941$0.453
$1.621 savings
When to use it
Good for
  • ●Backend services with no single dominant resource
  • ●Queue workers and scheduled jobs
  • ●Web and application servers with mixed CPU and memory demand
  • ●Workloads that fit inside 192 GiB of RAM
  • ●Parallel work that can occupy 48 vCPU
  • ●Network-heavy services — AWS rates this size at 18.75 Gigabit
  • ●Anything that shards cleanly across 3 nodes, which is how it maps onto Rackspace Spot
Avoid if
  • ●Starting a new deployment. m7a.12xlarge is the newer generation at this size.
  • ●The working set needs more than 192 GiB of RAM
  • ●Sustained full-core CPU load. A compute-optimized family costs less per unit of work.
  • ●More than 4.00 GiB of RAM per vCPU is needed — that ratio is fixed for the whole family
  • ●The work is single-threaded. Most of these 48 vCPU would sit idle.
  • ●Local NVMe or instance-store disk is a hard requirement
$1,514/mo on AWS on-demand against $90/mo on Rackspace Spot for the 3-node equivalent — market-priced, not list-priced.
  • 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