No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

<@U010EQ7PKKQ> I think this was fixed in 5.1.0 of the provider

Looks like we're actually already running 5.1.0 and still hitting this error. Has there been any movement on flipping the default bit for EC2 metadata access in the provider? <https://github.com/pulumi/pulumi-aws/issues/1692>

I don't think there's any movement on the defaults, if you set the env var/config value it should work

Unfortunately the env var doesn't seem to be having any impact

The config value was working on &lt;5.x but doesn't appear to be functional on 5.1

okay, that's definitely a bug. could you file an issue?

Hi <@U010EQ7PKKQ> - what env var were you setting?

I was using `AWS_EC2_METADATA_DISABLED=false`