I Checked the CPU and CloudTrail Information of the EC2 C9g Instances Now Available in the Tokyo Region
This page has been translated by machine translation. View original
Introduction
On September 3, 2026, EC2 C9g and C9gd instances powered by AWS Graviton5 became available in four Regions, including the Tokyo Region (ap-northeast-1).
On the same day, the general-purpose M9g and M9gd also became available in the Tokyo Region.
In this article, I launched a c9g.medium in the Tokyo Region, then confirmed the launch in CloudTrail and retrieved the CPU information.
Verification
Launching the instance
I launched a c9g.medium with the AWS CLI.
aws ec2 run-instances \
--region ap-northeast-1 \
--image-id ami-0abcde8261ecfaf82 \
--instance-type c9g.medium \
--subnet-id subnet-xxxxx \
--iam-instance-profile Name=ec2-ssm-core \
--associate-public-ip-address \
--metadata-options "HttpTokens=required,HttpEndpoint=enabled" \
--tag-specifications 'ResourceType=instance,Tags=[{Key=Name,Value=c9g-tokyo-verify}]' \
--query 'Instances[0].InstanceId' \
--output text
i-0123456789abcdef0
Confirming the launch in CloudTrail
After launching, I checked the RunInstances event in CloudTrail.
aws cloudtrail lookup-events \
--lookup-attributes AttributeKey=EventName,AttributeValue=RunInstances \
--start-time "2026-09-05T06:29:00+09:00" \
--end-time "2026-09-05T06:30:00+09:00" \
--region ap-northeast-1 \
--query 'Events[0].CloudTrailEvent' \
--output text | jq '.'
Here is an excerpt of the information from the launch event.
{
"eventTime": "2026-09-04T21:29:16Z",
"eventName": "RunInstances",
"awsRegion": "ap-northeast-1",
"requestParameters": {
"instanceType": "c9g.medium",
"instancesSet": {
"items": [{ "imageId": "ami-0abcde8261ecfaf82" }]
}
},
"responseElements": {
"instancesSet": {
"items": [
{
"instanceId": "i-0123456789abcdef0",
"instanceType": "c9g.medium",
"placement": {
"availabilityZone": "ap-northeast-1a"
},
"architecture": "arm64",
"launchTime": 1788557356000
}
]
}
}
}
We can confirm that the instanceType: c9g.medium specified in the CLI was launched in ap-northeast-1a and recorded in CloudTrail.
Verification environment
I launched one c9g.medium in ap-northeast-1a. The OS is Amazon Linux 2023.
instance-type: c9g.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 matched the values obtained in the M9g article. Since C9g and M9g use the same Graviton5 processor, there is no difference in the CPU information.
Full lscpu output
Architecture: aarch64
CPU op-mode(s): 64-bit
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 retrieved 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 is 0xd84, the same value as M9g.
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 M9g.
/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
lstopo-no-graphics
Machine (1797MB total)
Package L#0
NUMANode L#0 (P#0 1797MB)
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"
Pricing
I retrieved the Tokyo Region pricing with the Pricing API.
Comparing the ap-northeast-1 Linux On-Demand prices as of September 5, 2026 with C8g, C9g was +9.0% for all sizes listed in the table. Monthly costs are calculated based on 720 hours.
| Size | C9g (USD/hour) | C8g (USD/hour) | vs. C8g | C9g monthly (720 hours) | C8g monthly (720 hours) |
|---|---|---|---|---|---|
| medium | 0.05453 | 0.05003 | +9.0% | 39.26 | 36.02 |
| large | 0.10906 | 0.10006 | +9.0% | 78.52 | 72.04 |
| xlarge | 0.21812 | 0.20012 | +9.0% | 157.05 | 144.09 |
| 2xlarge | 0.43624 | 0.40024 | +9.0% | 314.09 | 288.17 |
| 4xlarge | 0.87248 | 0.80048 | +9.0% | 628.19 | 576.35 |
| 8xlarge | 1.74496 | 1.60096 | +9.0% | 1,256.37 | 1,152.69 |
| 12xlarge | 2.61744 | 2.40144 | +9.0% | 1,884.56 | 1,729.04 |
| 16xlarge | 3.48992 | 3.20192 | +9.0% | 2,512.74 | 2,305.38 |
| 24xlarge | 5.23488 | 4.80288 | +9.0% | 3,769.11 | 3,458.07 |
| 48xlarge | 10.46976 | 9.60576 | +9.0% | 7,538.23 | 6,916.15 |
| metal-48xl | 10.46976 | 9.60576 | +9.0% | 7,538.23 | 6,916.15 |
Comparing C9g in the Tokyo Region with us-east-1, the Tokyo price was +25.4% for all sizes listed in the table.
| Size | ap-northeast-1 (USD/hour) | us-east-1 (USD/hour) | vs. us-east-1 |
|---|---|---|---|
| medium | 0.05453 | 0.04347 | +25.4% |
| large | 0.10906 | 0.08694 | +25.4% |
| xlarge | 0.21812 | 0.17388 | +25.4% |
| 2xlarge | 0.43624 | 0.34776 | +25.4% |
| 4xlarge | 0.87248 | 0.69552 | +25.4% |
| 8xlarge | 1.74496 | 1.39104 | +25.4% |
| 12xlarge | 2.61744 | 2.08656 | +25.4% |
| 16xlarge | 3.48992 | 2.78208 | +25.4% |
| 24xlarge | 5.23488 | 4.17312 | +25.4% |
| 48xlarge | 10.46976 | 8.34624 | +25.4% |
| metal-48xl | 10.46976 | 8.34624 | +25.4% |
Comparing the compute-optimized C9g with the general-purpose M9g, both powered by Graviton5, C9g is about 14% cheaper than M9g for all sizes listed in the table.
| Size | C9g (USD/hour) | M9g (USD/hour) | C9g/M9g ratio |
|---|---|---|---|
| medium | 0.05453 | 0.06319 | -13.7% |
| large | 0.10906 | 0.12638 | -13.7% |
| xlarge | 0.21812 | 0.25276 | -13.7% |
| 2xlarge | 0.43624 | 0.50552 | -13.7% |
| 4xlarge | 0.87248 | 1.01104 | -13.7% |
| 8xlarge | 1.74496 | 2.02208 | -13.7% |
| 12xlarge | 2.61744 | 3.03312 | -13.7% |
| 16xlarge | 3.48992 | 4.04416 | -13.7% |
| 24xlarge | 5.23488 | 6.06624 | -13.7% |
| 48xlarge | 10.46976 | 12.13248 | -13.7% |
| metal-48xl | 10.46976 | 12.13248 | -13.7% |
C9g provides 2GB of memory per vCPU, half the memory capacity of M9g's 4GB/vCPU. For workloads that prioritize CPU performance over memory, choosing C9g can help reduce costs.
Summary
I launched the compute-optimized c9g.medium in ap-northeast-1a of the Tokyo Region. I confirmed the launch in CloudTrail and verified that the CPU information matches that of the general-purpose M9g.
The Linux On-Demand price of C9g is 9% higher than C8g, but AWS states that C9g offers up to 25% higher compute performance compared to the Graviton4-powered C8g. Also, compared to M9g with the same Graviton5, C9g is about 14% cheaper, making it a cost-efficient option for workloads that prioritize CPU performance over memory.
With this, the general-purpose M9g and the compute-optimized C9g are now available in the Tokyo Region. Once the memory-optimized R9g is available as well, you will be able to choose Graviton5 for major workloads. I look forward to R9g support in the Tokyo Region.
