Hi there 👋🏼 how do I have pulumi use the instance profile for the ec2 instance it's running on? Unfortunately my google-fu is failing me 😔 I expect y'all are delegating to the go client; I'm under the impression that will fallback to the meta data url but that doesn't seem to be happening.

There's a few ways to interpret your question. Can you clarify? Are you hoping to run Pulumi on an EC2 instance?

Yes

The AWS CLI does this implicitly, but Pulumi doesn't. There's instructions on how to set it up explicitly here: https://docs.aws.amazon.com/cli/latest/userguide/cli-configure-metadata.html

@little-cartoon-10569 I'll give it a go. File this under TIL

You may also need to set AWS_PROFILE to be the profile you create with that info? Not 100% on that...

RE: AWS_PROFILE the docs state that - but it seems if it's the default profile you don't have to do that. Ultimately, I think this is not what I want. The problem then devolves into trust relationships which get's a bit chicken:egg-esque because the instance itself is managed by pulumi. AWS_ACCESS_KEY here I come! Thanks anyways @little-cartoon-10569

You might want to consider using this technique to get a base profile, then assuming an explicit role from there?