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

Now should this be automatic? Because the roles are attached to the pod/worker node there is no aws_credentials etc. so this would mean that Pulumi will not be able to view the  ./aws/ folder for configs

not 100% sure if this is what you want. But we explicitly state what gets what provider in aws using <https://www.pulumi.com/docs/reference/pkg/nodejs/pulumi/aws/#Provider>

here is an example that should help. They actually get the roleArn from a different stack which you may or may not need. <https://github.com/pulumi/examples/blob/master/aws-ts-assume-role/assume-role/index.ts>

essentially make a provider, pass it to things that you want to have explicitly use that provider

also you don't have to have a `./aws/credentials` file you can simply export
```export AWS_ACCESS_KEY_ID=blahblah
export AWS_SECRET_ACCESS_KEY=alsdfalsdf```

thanks <@UR42L3L73> So the mandate was no Access Key or Secret Key. To just use the role provided by the Service Account. I will look into the examples you gave thanks  :slightly_smiling_face: