AWS has opened general availability for two new EC2 instance families — M9g and M9gd — built on the Graviton5 processor that was previewed at re:Invent 2025. The move takes the fifth-generation custom silicon out of early access and into standard purchasing channels across four AWS regions: US East (N. Virginia), US East (Ohio), US West (Oregon), and Europe (Frankfurt).
- Graviton5 delivers up to 25% better compute performance than Graviton4-based instances
- Up to 35% faster for web apps and ML inference; up to 30% for databases
- 5× larger L3 cache and DDR5-8800 memory versus the prior generation
- M9gd offers up to 11.4 TB of local NVMe SSD with 30% higher IOPS than M8gd
- Available on-demand, spot, savings plans, dedicated instances, and dedicated hosts
What changed in the silicon
Graviton5 is the first AWS processor to use PCIe Gen6 and DDR5-8800 memory, giving it what AWS describes as the highest memory bandwidth among processor instances currently offered in the cloud. The chip scales to 192 cores and carries five times the L3 cache of Graviton4, with inter-core latency reduced by up to a third. Those cache and latency figures are particularly relevant for workloads that shuttle data between threads frequently — databases, JVM-based services, and the orchestration layers common in multi-step AI pipelines.
On the I/O side, M9g and M9gd instances add roughly 15% more network bandwidth and 20% more EBS bandwidth on average across sizes compared to their M8g predecessors, with the largest 48xlarge configuration reaching 100 Gbps network and 72 Gbps EBS. The families also support Instance Bandwidth Configuration, which lets operators shift up to 25% of total bandwidth allocation between EBS and VPC networking without resizing the instance — useful for tuning database write-heavy vs. read-heavy phases.
A new hypervisor isolation model
The M9g launch introduces the Nitro Isolation Engine, a component AWS is positioning as an industry first. Rather than relying solely on conventional testing, the engine uses formal verification — mathematical proof techniques — to demonstrate that the hypervisor correctly enforces memory, CPU register, and I/O boundaries between virtual machines. AWS states this makes Nitro the first formally verified cloud hypervisor. For operators running multi-tenant or regulated workloads, this provides a qualitatively different class of assurance than coverage-based QA alone.
Customer benchmarks from the preview period
Three early adopters published production results during the preview. ClickHouse reported a 36% throughput gain over M8g with no code modifications. Honeycomb ran a six-month A/B test against Graviton4 production infrastructure and measured 36% better throughput per core. HubSpot deployed M9g for MySQL and saw query durations fall by as much as 60%. AWS also disclosed that Meta is adopting Graviton at scale — starting with tens of millions of cores — to support agentic AI workloads, making it one of the platform's largest customers.
Relevance for infrastructure teams
For teams already on M8g or earlier Graviton instances, the upgrade path is straightforward: Graviton5 maintains Arm binary compatibility, and AWS offers the Transform service to automate x86-to-Graviton code migration for Java applications. The Graviton Savings Dashboard can be used to model cost differences before committing.
The M9gd variant adds local NVMe storage for workloads that benefit from low-latency scratch space — caching layers, log pipelines, and key-value stores — ranging from 59 GB on the medium size up to three 3.8 TB drives on the 48xlarge and bare-metal configurations.
Both families now sit within the standard EC2 purchasing model. AWS notes Graviton currently underpins more than 350 instance types serving over 120,000 customers, giving the ecosystem a wide base of compatible AMIs, managed services, and third-party tooling.
Automated pipeline · Cloud & Infrastructure
Synthesized from 1 industry feed on 13 Jun 2026. Passed independent editor verification before publication. Style guide v1.1.
Sources
Decision trail
- Checking for duplicates — New story AWS launches new Graviton5-powered EC2 instances with improved performance.
- Writing the article — Draft created article_id=5 slug=aws-graviton5-powered-m9g-and-m9gd-instances-reach-general-availability
-
Editor review — Approved
- Factual grounding: Minor: The article states inter-core latency is 'reduced by up to a third.' The source says 'up to 33% lower inter-core latency,' which is consistent with 'up to a third' — this is acceptable paraphrase, not a material error.
- Factual grounding: Minor: The article says the largest 48xlarge reaches '100 Gbps network and 72 Gbps EBS.' The source tables confirm this for both 48xlarge and metal-48xl. Accurate.
- Factual grounding: Minor: The article says M9gd ranges 'from 59 GB on the medium size up to three 3.8 TB drives on the 48xlarge and bare-metal configurations.' The source confirms 1x59 NVMe SSD for medium and 3x3800 NVMe SSD for 48xlarge and metal-48xl. Accurate.
- Factual grounding: Minor: The article says AWS Transform handles 'Java applications' migrating from x86 to Graviton. The source confirms this. Accurate.
- Factual grounding: Material concern (borderline): The article says Graviton5 delivers 'the highest memory bandwidth among processor instances currently offered in the cloud.' The source says 'deliver the fastest memory of any processor instances in the cloud.' The article's rephrasing ('highest memory bandwidth') slightly changes the meaning — the source says 'fastest memory,' not specifically 'highest memory bandwidth.' This is a subtle but potentially meaningful difference. Assessed as minor given the proximity of meaning.
- Factual grounding: Minor: The article says 'up to twice the network bandwidth for the largest instance size' is supported by the source but not explicitly stated in the article body — this claim from the source is omitted, not misrepresented. No issue.
- Factual grounding: Minor: The article states M9gd has '3 x 3.8 TB drives on the 48xlarge.' The source table lists '3 x 3800 NVMe SSD' for 48xlarge, which equals 3 x 3.8 TB. Accurate.
- Style compliance: Minor: Word count appears to be approximately 680-700 words in the body, which is within the hard maximum of 750 but above the 620-word target range. This is a minor style issue.
- Factual grounding: Minor: The article states IBC lets operators 'shift up to 25% of total bandwidth allocation between EBS and VPC networking.' The source says 'adjust the allocation of bandwidth between Amazon EBS and Amazon Virtual Private Cloud (Amazon VPC) networking for an Amazon EC2 instance by up to 25%.' The article's phrasing is consistent with the source meaning.
- Factual grounding: Minor: The article describes the Nitro Isolation Engine as 'an industry first' and says it uses 'formal verification — mathematical proof techniques — to demonstrate that the hypervisor correctly enforces memory, CPU register, and I/O boundaries.' This closely mirrors source language about 'mediation of all access to virtual machine memory, CPU register state, and I/O devices.' The idea is paraphrased adequately, though the enumeration is similar. Not a material copy.
- No copied phrasing: Minor: 'five times the L3 cache of Graviton4' is very close to source phrasing '5 times more L3 cache compared to the previous generation.' This is a borderline case but the restructuring is minimal. Could be paraphrased more distinctly.
- Assigning hero image — Pexels pexels_id=17489150
- Linking related stories — Linked 0 relations from 0 candidates
- Linking related stories — Linked 0 relations from 0 candidates
- Publishing — Published aws-graviton5-powered-m9g-and-m9gd-instances-reach-general-availability

Discussion · coming soon
Be the first to join the thread when community discussion launches.