Skip to content

(ec2): Add support for M9g and M9gd (Graviton5) instance types #7029

@tschoonj

Description

@tschoonj

Describe the feature

AWS recently announced general availability of the M9g and M9gd EC2 instance types, powered by AWS Graviton5 processors:

https://aws.amazon.com/about-aws/whats-new/2026/06/ec2-m9g-m9gd-instances-graviton5-processors-available/

These instances are available in several regions, including EU (Frankfurt) / eu-central-1, which is where we intend to use them.

However, the EC2 InstanceType enum does not yet recognize these new types. The enum is generated from the EC2 service model (services/ec2/src/main/resources/codegen-resources/service-2.json), and as of the latest release (2.46.8) — and even on the current master branch — that model contains m8g/m8gd entries but no m9g/m9gd entries (in fact no m9 family at all). The highest m generation present is gen-8.

As a result, software.amazon.awssdk.services.ec2.model.InstanceType.fromValue("m9g.large") (and the various m9g/m9gd sizes, including the m9gd NVMe-backed variants) resolves to UNKNOWN_TO_SDK_VERSION rather than a real enum value. This breaks calls such as DescribeInstanceTypes and DescribeSpotPriceHistory when those instance types are passed via the strongly-typed InstanceType enum.

Could you please update the EC2 service model to include the new M9g and M9gd instance types so they are available through the InstanceType enum in an upcoming release? Thank you.

Use Case

We are rolling out M9g/M9gd (Graviton5) instances for ARM64 compute in eu-central-1. Our application uses the EC2 client (DescribeInstanceTypes, DescribeSpotPriceHistory) with the typed InstanceType enum to fetch instance specifications and spot pricing. Without the enum values for these new types, those lookups fail and we cannot retrieve specs/pricing for the new instances.

Proposed Solution

Update services/ec2/src/main/resources/codegen-resources/service-2.json to add the m9g.* and m9gd.* instance type values to the InstanceType enum (matching the sizes available for the family), so they are generated into software.amazon.awssdk.services.ec2.model.InstanceType and ship in a subsequent release.

Other Information

Acknowledgements

  • I may be able to implement this feature request

AWS Java SDK version used

2.40.9 (also verified the model is missing the types in 2.46.8 / master)

JDK version used

N/A

Operating System and version

N/A

Metadata

Metadata

Assignees

No one assigned

    Labels

    feature-requestA feature should be added or improved.service-apiThis issue is due to a problem in a service API, not the SDK implementation.service:ec2

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions