aws-ec2: Expose EC2 instance MetadataOptions

[luxaritas]

Describe the feature

According to aws-cloudformation/cloudformation-coverage-roadmap#655 (comment), EC2 Instance MetadataOptions are now available via CFN. Previously, this was only available for launch templates. The properties here should be exposed as instance parameters, just like they have been in launch templates

Use Case

Support to enable instance metadata tags, HTTP response hop limit, etc without using a launch template

Proposed Solution

No response

Other Information

Normally I would offer to do this myself, but I unfortunately don't have the bandwidth - I expect this should be straightforward though!

Acknowledgements

• I may be able to implement this feature request
• This feature might incur a breaking change

AWS CDK Library version (aws-cdk-lib)

2.213.0

AWS CDK CLI version

2.1027.0

Environment details (OS name and version, etc.)

Manjaro Linux 25.0.7

[pahud]

Hi @luxaritas,

Thanks for this feature request! This makes a lot of sense and would definitely improve the developer experience for configuring EC2 instance metadata options.

EC2 Instance MetadataOptions are now available via CloudFormation (as confirmed in the CloudFormation coverage roadmap). Currently, our Instance construct only exposes the requireImdsv2 boolean property, which is more limited than what's available in LaunchTemplate.

This enhancement would allow users to:

• Enable instance metadata tags
• Configure HTTP response hop limit
• Set HTTP endpoint availability
• Control HTTP tokens requirement
• And other metadata options without requiring a launch template

We'd welcome a PR contribution for this feature! The implementation would involve:

1. Adding a metadataOptions property to InstanceProps similar to the one in LaunchTemplateProps
2. Updating the CfnInstance creation to include the metadata options
3. Ensuring backward compatibility with the existing requireImdsv2 property
4. Adding appropriate validation and tests

This would be a straightforward enhancement that aligns with the existing patterns in our Launch Template implementation.

[github-actions]

Comments on closed issues and PRs are hard for our team to see.
If you need help, please open a new issue that references this one.