Hi, I am trying out pulumi w/ AWS but I can't eve...
# aws
r
Hi, I am trying out pulumi w/ AWS but I can't even get the first example up. Pulumi up is just stuck. Was able to get the logs
Copy code
▶ pulumi up --logtostderr -v=9 2> out.txt
Previewing update (dev):

     Type                 Name             Plan        
     pulumi:pulumi:Stack  pulumi-demo-dev  running
Logs stuck at
Copy code
I0212 21:31:53.571144   74172 eventsink.go:63] eventSink::Debug(<{%reset%}>Trying to get account information via sts:GetCallerIdentity<{%reset%}>)
b
Hi @rapid-oyster-28892 can you share what example code you are running?
r
the code from
Copy code
pulumi new aws-javascript
config is
Copy code
config:
  aws:profile: foo
  aws:region: ap-southeast-1
  pulumi:template: aws-javascript
b
Mmmhhh
What version of Pulumi and the aws provider are you using?
r
Copy code
"@pulumi/pulumi": "^1.0.0",
        "@pulumi/aws": "^1.0.0",
        "@pulumi/awsx": "^0.18.10"
Copy code
▶ pulumi version
v1.10.1
b
Ok I can try and replicate this and see what the issue is
And your credentials from your profile work when running aws CLi commands?
r
yes
b
Mmmhhhh
Ok
Will look at this and see
r
they are just static aws access keys btw
b
Not at my laptop for the next hour but will check back in
r
sure, no prob.
b
Can you do me a massive favour and set them as EnvVars and see if that works for you?
So remove aws:profile and let it read your access key and secret key as env vars
r
ok let me try
b
I am wondering if there’s an issue with profiles...
r
this shouldn't take too long right? probably running for about a minute now.
b
It should run immediately
Can you tell me what node version you are running?
r
Copy code
▶ node -v
v10.16.3
b
Ok this is all very strange
Let me get back to you on this
Thanks for helping try and narrow down the issue - sorry for it not working
r
alright
i'll check if I can find something as well
ok, I saw this issue https://github.com/pulumi/pulumi-aws/issues/873 and I just blindly just decided to set the configs
Copy code
aws:skipCredentialsValidation: "true"
  aws:skipMetadataApiCheck: "true"
  aws:skipRequestingAccountId: "true"
and it now works
b
Ah... so it was a timing thing - ok I guess we need to work on adding defaults for those
Thanks for validating thatbissue
Can you add to it to show that you hit it as well?
TIA
r
it seems like
aws:skipCredentialsValidation: "true"
is the actual setting that made it work.
if I remove that one and retain the others it still hangs up.
is there any other info you might want me to add into that issue?