This message was deleted.

sparse-intern-71089

11/15/2019, 9:30 PM

This message was deleted.

white-balloon-205

11/15/2019, 9:34 PM

I tried something similar to this and it worked for me. Are you providing credentials to the input to your

Provider

? (or getting them from ambient AWS configuration?)

billowy-laptop-45963

11/15/2019, 9:34 PM

Weird running pulumi up like

AWS_SDK_LOAD_CONFIG=true pulumi up

fixed the above.

billowy-laptop-45963

11/15/2019, 9:34 PM

I've been using that provider fine for building everything else

white-balloon-205

11/15/2019, 9:35 PM

Ahh - are your credentials in

~/.aws/config

? Are you using a

profile

here?

billowy-laptop-45963

11/15/2019, 9:35 PM

billowy-laptop-45963

11/15/2019, 9:35 PM

provider is defined like above where profile is the profile name to use.

billowy-laptop-45963

11/15/2019, 9:37 PM

I think this might be a bug somewhere since I don't need AWS_SDK_LOAD_CONFIG=true for the resources, only those data calls

white-balloon-205

11/15/2019, 9:37 PM

Yes - this does sound like it might be a bug. Could you open an issue to track this?

billowy-laptop-45963

11/15/2019, 9:37 PM

sure

billowy-laptop-45963

11/15/2019, 9:50 PM

https://github.com/pulumi/pulumi-aws/issues/794

👍 1

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.