# AWS EC2 IMDSv2

**URL:** <https://discuss.rapid7.com/t/aws-ec2-imdsv2/40686>\
**Category:** Community\
**Tags:** InsightVM, InsightIDR, aws\_ec2, aws\
**Created:** [August 6, 2024, 8:36am UTC](https://discuss.rapid7.com/t/aws-ec2-imdsv2/40686 "2024-08-06T08:36:47Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![eogden](https://discuss.rapid7.com/letter_avatar_proxy/v4/letter/e/3ec8ea/32.png) [@eogden](https://discuss.rapid7.com/u/eogden)\
**Post date:** [August 6, 2024, 8:36am UTC](https://discuss.rapid7.com/t/aws-ec2-imdsv2/40686/1 "2024-08-06T08:36:47Z")

</div>

As of March 2024 AWS have started setting IMDSv2 to required by default REF [https://aws.amazon.com/about-aws/whats-new/2024/03/set-imdsv2-default-new-instance-launches/](https://aws.amazon.com/about-aws/whats-new/2024/03/set-imdsv2-default-new-instance-launches/)

As I understand currently this has to be set to optional because the Rapid7 applications running in the EC2 instances don’t support IMDSv2.

Where they haven’t announced the depreciation of IMDSv1 I’m sure they will soon.

Anyone else having this issue or has it now been solved?