Checking the CPU Information on the EC2 M9g Instance (Graviton5), Now Available in the Tokyo Region
This page has been translated by machine translation. View original
Introduction
On September 3, 2026, EC2 M9g and M9gd instances powered by AWS Graviton5 became available in four regions, including the Tokyo region (ap-northeast-1).
At the North American GA, I launched an m9g.medium in us-east-1 and checked its CPU information.
In this article, I ran the same OS commands on an m9g.medium in the Tokyo region and checked its CPU information.
Verification
Verification environment
I launched one m9g.medium in ap-northeast-1a. The OS is Amazon Linux 2023.
instance-type: m9g.medium
availability-zone: ap-northeast-1a
ami-id: ami-0abcde8261ecfaf82
kernel: 6.18.44-99.149.amzn2023.aarch64
PRETTY_NAME="Amazon Linux 2023.12.20260831"
CPU information
I ran lscpu. Here are the key points of the output.
Architecture: aarch64
BIOS Vendor ID: AWS
BIOS Model name: AWS Graviton5
Stepping: r0p1
Flags: fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp asimdhp cpuid asimdrdm jscvt fcma lrcpc dcpop sha3 asimddp sha512 sve asimdfhm dit uscat ilrcpc flagm sb paca pacg dcpodp sve2 sveaes svepmull svebitperm svesha3 flagm2 frint svei8mm svebf16 i8mm bf16 dgh rng bti ecv afp wfxt
L1d cache: 64 KiB (1 instance)
L1i cache: 64 KiB (1 instance)
L2 cache: 2 MiB (1 instance)
L3 cache: 48 MiB (1 instance)
All the items listed here matched the values obtained from the m9g.medium in us-east-1 in the earlier article.
Full lscpu output
Byte Order: Little Endian
CPU(s): 1
On-line CPU(s) list: 0
Vendor ID: ARM
BIOS Vendor ID: AWS
BIOS Model name: AWS Graviton5
Model: 1
Thread(s) per core: 1
Core(s) per socket: 1
Socket(s): 1
Stepping: r0p1
BogoMIPS: 2000.00
Flags: fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp asimdhp cpuid asimdrdm jscvt fcma lrcpc dcpop sha3 asimddp sha512 sve asimdfhm dit uscat ilrcpc flagm sb paca pacg dcpodp sve2 sveaes svepmull svebitperm svesha3 flagm2 frint svei8mm svebf16 i8mm bf16 dgh rng bti ecv afp wfxt
L1d cache: 64 KiB (1 instance)
L1i cache: 64 KiB (1 instance)
L2 cache: 2 MiB (1 instance)
L3 cache: 48 MiB (1 instance)
NUMA node(s): 1
NUMA node0 CPU(s): 0
I obtained the processor information with dmidecode.
Processor Information
Family: ARMv9
Manufacturer: AWS
ID: 41 D8 0F 41 00 00 00 00
Signature: Implementor 0x41, Variant 0x0, Architecture 15, Part 0xd84, Revision 1
Version: AWS Graviton5
Max Speed: 3300 MHz
Current Speed: 3300 MHz
Core Count: 1
The CPU part was 0xd84, the same value as in us-east-1 in the earlier article.
Full dmidecode -t processor output
# dmidecode 3.6
Getting SMBIOS data from sysfs.
SMBIOS 3.0.0 present.
Handle 0x0004, DMI type 4, 42 bytes
Processor Information
Socket Designation: CPU0
Type: Central Processor
Family: ARMv9
Manufacturer: AWS
ID: 41 D8 0F 41 00 00 00 00
Signature: Implementor 0x41, Variant 0x0, Architecture 15, Part 0xd84, Revision 1
Version: AWS Graviton5
Voltage: Unknown
External Clock: Unknown
Max Speed: 3300 MHz
Current Speed: 3300 MHz
Status: Populated, Enabled
Upgrade: None
L1 Cache Handle: Not Provided
L2 Cache Handle: Not Provided
L3 Cache Handle: Not Provided
Serial Number: AWS Graviton5
Asset Tag: AWS Graviton5
Part Number: AWS Graviton5
Core Count: 1
Core Enabled: 1
Thread Count: 1
Characteristics: None
I checked the SVE vector length.
cat /proc/sys/abi/sve_default_vector_length
16
The vector length is 16 bytes (128 bits), no different from us-east-1.
Below is supplementary information obtained from the same instance.
/proc/cpuinfo
processor : 0
BogoMIPS : 2000.00
Features : fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp asimdhp cpuid asimdrdm jscvt fcma lrcpc dcpop sha3 asimddp sha512 sve asimdfhm dit uscat ilrcpc flagm sb paca pacg dcpodp sve2 sveaes svepmull svebitperm svesha3 flagm2 frint svei8mm svebf16 i8mm bf16 dgh rng bti ecv afp wfxt
CPU implementer : 0x41
CPU architecture: 8
CPU variant : 0x0
CPU part : 0xd84
CPU revision : 1
lscpu Vulnerabilities section
Vulnerability Gather data sampling: Not affected
Vulnerability Ghostwrite: Not affected
Vulnerability Indirect target selection: Not affected
Vulnerability Itlb multihit: Not affected
Vulnerability L1tf: Not affected
Vulnerability Mds: Not affected
Vulnerability Meltdown: Not affected
Vulnerability Mmio stale data: Not affected
Vulnerability Old microcode: Not affected
Vulnerability Reg file data sampling: Not affected
Vulnerability Retbleed: Not affected
Vulnerability Spec rstack overflow: Not affected
Vulnerability Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl
Vulnerability Spectre v1: Mitigation; __user pointer sanitization
Vulnerability Spectre v2: Mitigation; CSV2, BHB
Vulnerability Srbds: Not affected
Vulnerability Tsa: Not affected
Vulnerability Tsx async abort: Not affected
Vulnerability Vmscape: Not affected
lstopo-no-graphics
Machine (3776MB total)
Package L#0
NUMANode L#0 (P#0 3776MB)
L3 L#0 (48MB) + L2 L#0 (2048KB) + L1d L#0 (64KB) + L1i L#0 (64KB) + Core L#0 + PU L#0 (P#0)
HostBridge
PCI 00:04.0 (NVMExp)
Block(Disk) "nvme0n1"
HostBridge
PCIBridge
PCIBridge
PCIBridge
PCI 27:00.0 (Ethernet)
Net "ens34"
nvme id-ctrl (excerpt)
NVME Identify Controller:
vid : 0x1d0f
ssvid : 0x1d0f
mn : Amazon Elastic Block Store
fr : 2.0
rab : 32
ieee : a002dc
mdts : 6
cntlid : 0
ver : 0x10400
Kernel log
I checked the CPU features detected at boot using dmesg.
[ 0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd841]
[ 0.000000] Detected PIPT I-cache on CPU0
[ 0.000000] CPU features: detected: Address authentication (architected QARMA3 algorithm)
[ 0.000000] CPU features: detected: Spectre-v4
[ 0.000000] CPU features: detected: Spectre-BHB
[ 0.000970] CPU features: detected: Branch Target Identification
[ 0.000977] CPU features: detected: Enhanced Counter Virtualization
[ 0.000980] CPU features: detected: Generic authentication (architected QARMA3 algorithm)
[ 0.000981] CPU features: detected: LSE atomic instructions
[ 0.000984] CPU features: detected: Random Number Generator
[ 0.000986] CPU features: detected: WFx with timeout
[ 0.000988] CPU features: detected: Scalable Vector Extension
[ 0.001809] SVE: maximum available vector length 16 bytes per vector
[ 0.001810] SVE: default vector length 16 bytes per vector
Pointer authentication (QARMA3), BTI, LSE atomic instructions, the random number generator, and SVE were all detected. The maximum SVE vector length was also 16 bytes.
Pricing
I retrieved the Tokyo region pricing using the Pricing API.
# Example of retrieving the m9g.medium price (ap-northeast-1 / Linux / On-Demand)
aws pricing get-products \
--region us-east-1 \
--service-code AmazonEC2 \
--filters \
'Type=TERM_MATCH,Field=instanceType,Value=m9g.medium' \
'Type=TERM_MATCH,Field=location,Value=Asia Pacific (Tokyo)' \
'Type=TERM_MATCH,Field=operatingSystem,Value=Linux' \
'Type=TERM_MATCH,Field=tenancy,Value=Shared' \
'Type=TERM_MATCH,Field=preInstalledSw,Value=NA' \
'Type=TERM_MATCH,Field=capacitystatus,Value=Used' \
--query 'PriceList'
The Pricing API endpoint is specified as us-east-1, so even when retrieving Tokyo region pricing, you run it with --region us-east-1. The instanceType filter does not accept wildcards. To retrieve all sizes at once, narrow down by instanceFamily (the value is General purpose).
Comparing the ap-northeast-1 Linux On-Demand pricing as of September 5, 2026 with m8g, all sizes listed in the table were +9.0%. Monthly costs are calculated based on 720 hours.
| Size | m9g (USD/hour) | m8g (USD/hour) | vs. m8g | m9g monthly (720 hours) | m8g monthly (720 hours) |
|---|---|---|---|---|---|
| medium | 0.06319 | 0.05797 | +9.0% | 45.50 | 41.74 |
| large | 0.12638 | 0.11594 | +9.0% | 90.99 | 83.48 |
| xlarge | 0.25276 | 0.23188 | +9.0% | 181.99 | 166.95 |
| 2xlarge | 0.50552 | 0.46376 | +9.0% | 363.97 | 333.91 |
| 4xlarge | 1.01104 | 0.92752 | +9.0% | 727.95 | 667.81 |
| 8xlarge | 2.02208 | 1.85504 | +9.0% | 1,455.90 | 1,335.63 |
| 12xlarge | 3.03312 | 2.78256 | +9.0% | 2,183.85 | 2,003.44 |
| 16xlarge | 4.04416 | 3.71008 | +9.0% | 2,911.80 | 2,671.26 |
| 24xlarge | 6.06624 | 5.56512 | +9.0% | 4,367.69 | 4,006.89 |
| 48xlarge | 12.13248 | 11.13024 | +9.0% | 8,735.39 | 8,013.77 |
| metal-48xl | 12.13248 | 11.13024 | +9.0% | 8,735.39 | 8,013.77 |
Comparing M9g in the Tokyo region with us-east-1, the Tokyo pricing was +29.2% for all sizes listed in the table.
| Size | ap-northeast-1 (USD/hour) | us-east-1 (USD/hour) | vs. us-east-1 |
|---|---|---|---|
| medium | 0.06319 | 0.04892 | +29.2% |
| large | 0.12638 | 0.09784 | +29.2% |
| xlarge | 0.25276 | 0.19568 | +29.2% |
| 2xlarge | 0.50552 | 0.39136 | +29.2% |
| 4xlarge | 1.01104 | 0.78272 | +29.2% |
| 8xlarge | 2.02208 | 1.56544 | +29.2% |
| 12xlarge | 3.03312 | 2.34816 | +29.2% |
| 16xlarge | 4.04416 | 3.13088 | +29.2% |
| 24xlarge | 6.06624 | 4.69632 | +29.2% |
| 48xlarge | 12.13248 | 9.39264 | +29.2% |
| metal-48xl | 12.13248 | 9.39264 | +29.2% |
Summary
I launched an m9g.medium with Amazon Linux 2023 in ap-northeast-1a in the Tokyo region. The CPU information confirmed on the one instance launched this time matched what was obtained in us-east-1 at the North American GA.
The Linux On-Demand pricing for M9g is 9% higher than M8g, but AWS states that M9g offers up to 25% higher compute performance compared to the Graviton4-powered M8g. If you are using M8g or earlier AWS Graviton instances in the Tokyo region, try running the same workload on M9g and compare performance and pricing.
