# IMDSv2 Support

**URL:** <https://meta.discourse.org/t/imdsv2-support/272379>\
**Category:** Self-hosting\
**Created:** [July 21, 2023, 9:50am UTC](https://meta.discourse.org/t/imdsv2-support/272379 "2023-07-21T09:50:44Z")\
**Posts on this page:** 1\
**Showing post:** 18

<div class="post-metadata">

**Author:** ![supermathie](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/supermathie/32/507518_2.png) [@supermathie](https://meta.discourse.org/u/supermathie)\
**Post date:** [November 24, 2025, 5:25pm UTC](https://meta.discourse.org/t/imdsv2-support/272379/18 "2025-11-24T17:25:46Z")

</div>

This is great to know!

And hopefully this applies to others as well.

But I’m wondering why this isn’t a problem for us. We have this set to 1 and yet it works?

```plaintext
discourse(prod)> ENV['AWS_EC2_METADATA_V1_DISABLED'] = 'true'
=> "true"
discourse(prod)> c = Aws::S3::Client.new(region: ENV['DISCOURSE_S3_REGION'])
=> #<Aws::S3::Client>
discourse(prod)> c.config.credentials.disable_imds_v1
=> true
discourse(prod)> c.list_objects_v2(bucket: ENV['DISCOURSE_S3_BUCKET']).contents.count
=> 1000

```

and that instance has this metadata as per the same query command:

```plaintext
{
    "State": "applied",
    "HttpTokens": "optional",
    "HttpPutResponseHopLimit": 1,
    "HttpEndpoint": "enabled",
    "HttpProtocolIpv6": "disabled",
    "InstanceMetadataTags": "disabled"
}

```

We’re running Discourse in a docker container on EC2, same as others, so… what’s the difference?

---

_[View the full topic](https://meta.discourse.org/t/imdsv2-support/272379)._