This message was deleted.

sparse-intern-71089

12/12/2019, 8:03 PM

This message was deleted.

astonishing-cartoon-37000

12/12/2019, 8:38 PM

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

astonishing-cartoon-37000

12/12/2019, 8:39 PM

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

astonishing-cartoon-37000

12/12/2019, 8:40 PM

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

astonishing-cartoon-37000

12/12/2019, 8:41 PM

also you don't have to have a

./aws/credentials

file you can simply export

Copy code

export AWS_ACCESS_KEY_ID=blahblah
export AWS_SECRET_ACCESS_KEY=alsdfalsdf

thankful-optician-22583

12/12/2019, 10:58 PM

thanks @astonishing-cartoon-37000 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 🙂

Open in Slack

Previous Next

Pulumi Community

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.