I am writing to inquire about the support of IMDSv2 through instance profiles in Discourse. We are in the process of migrating our service to use IMDSv2, as IMDSv1 is not an secure option. We would like to understand if Discourse currently supports IMDSv2 through instance profiles and if not, what …

I’m not aware of any way that Discourse itself uses IMDS. Have you installed Discourse on AWS somehow? Are you somehow using IMDSv1 with Discourse already? What is your use case?

I found one related code. spec/lib/s3_helper_spec.rb v3.1.0.beta5 </Rule> </LifecycleConfiguration> XML end it "can correctly set the purge policy" do SiteSetting.s3_configure_tombstone_…

[immagine] chocecil: I found one related code. discourse/spec/lib/s3_helper_spec.rb at v3.1.0.beta5 · discourse/discourse · GitHub This is in the testing spec. Discourse uses a version of the AWS SDK (3.130.2) above the minimum required to support IMDSv2 and from what I can tell looking at …

We started using Discourse on an AWS EC2 instance a year ago. And this week we updated our instance to only use IMDSv2, this broke our AWS S3 uploads with the error message “unable to sign request without credentials set”. We also utilise the “s3 use iam profile” setting. The local IMDS service is …

We are also seeing this backup issue after disabling IMDSv1 due to security reasons. We can see the use of IMDSv1 (in 3.3.0.beta1-dev) via the MetadataNoToken metric, so we are wondering what version of Discourse switched to using v2 everywhere?

We too were bitten by this today once we changed our AWS instance to use IMDSv2 only: our users could no longer upload images to S3. Probably relevant here: we are also using the s3 use iam profile option. For now we switched it to “Optional” which basically means IMDSv1 is still enabled which isn…

Does anyone had a solution/workaround to have Discourse work wit IMDSv2?

We are making changes to allow/expect more configuration to be possible via the .aws/config file which might happen to overlap with this and make it possible.

@supermathie the most weird thing that I cannot figure out is that I personally set up 2 discourse instances (dev/prod) that are identically configured (s3 uploads for files and backup using IAM profile) and updated to identical version ( 9436f5e3d4 ) and when I disabled IMDSv1… in dev everything kept…

@ducks identified the timeouts in the SDK for acquiring IMDS credentials are very aggressive (1 second, no retries) so it’s possible that it’s hitting that timeout. But that’s just a guess. If you console into prod can you do it interactively, e.g.: discourse(prod)> c = Aws::S3::Client.new(region…

Supporto IMDSv2

Supporto Installazione

pfaffman (Jay Pfaffman) 21 Luglio 2023, 7:01pm 3

Non sono a conoscenza di alcun modo in cui Discourse stesso utilizzi IMDS. Hai installato Discourse su AWS in qualche modo? Stai in qualche modo utilizzando IMDSv1 con Discourse già?

Qual è il tuo caso d’uso?

Argomento		Risposte	Visualizzazioni
Backups to S3 fail when IMDSv1 disabled Bug backups , s3	0	127	Agosto 29, 2024
How are you authenticating Discourse to AWS? Help us improve the settings! Feature s3	3	245	Ottobre 9, 2025
Set up file and image uploads to S3 Self-Hosting configuring , how-to	35	121584	Ottobre 25, 2025
Configure an S3 compatible object storage provider for uploads Self-Hosting cdn , configuring , how-to , reference	267	52424	Settembre 15, 2026
Problems with Patreon Login, Force HTTPS, and S3 CDN (three) Issues Self-hosting unsupported-install	12	2309	Gennaio 6, 2023

Supporto IMDSv2

Argomenti correlati