This message was deleted.
# awss
sparse-intern-71089
05/28/2020, 2:46 AMThis message was deleted.
g
glamorous-printer-14057
05/28/2020, 2:46 AMrunning
pulumi up --logtostderr -v=9 Copy code
I0527 19:44:28.526972 46303 eventsink.go:59] Ignoring AWS metadata API endpoint at default location as it doesn't return any instance-id
I0527 19:44:28.526989 46303 eventsink.go:62] eventSink::Debug(<{%reset%}>Ignoring AWS metadata API endpoint at default location as it doesn't return any instance-id<{%reset%}>)
I0527 19:44:28.527333 46303 eventsink.go:59] AWS Auth provider used: "EnvProvider"
I0527 19:44:28.527344 46303 eventsink.go:62] eventSink::Debug(<{%reset%}>AWS Auth provider used: "EnvProvider"<{%reset%}>)
I0527 19:44:28.527823 46303 eventsink.go:59] Trying to get account information via sts:GetCallerIdentity
I0527 19:44:28.527832 46303 eventsink.go:62] eventSink::Debug(<{%reset%}>Trying to get account information via sts:GetCallerIdentity<{%reset%}>)
I0527 19:44:28.538582 46303 eventsink.go:59] Ignoring AWS metadata API endpoint at default location as it doesn't return any instance-id
I0527 19:44:28.538599 46303 eventsink.go:62] eventSink::Debug(<{%reset%}>Ignoring AWS metadata API endpoint at default location as it doesn't return any instance-id<{%reset%}>)
I0527 19:44:28.538994 46303 eventsink.go:59] AWS Auth provider used: "EnvProvider"
I0527 19:44:28.539003 46303 eventsink.go:62] eventSink::Debug(<{%reset%}>AWS Auth provider used: "EnvProvider"<{%reset%}>)
I0527 19:44:28.539355 46303 eventsink.go:59] Trying to get account information via sts:GetCallerIdentity
pulumi:pulumi:Stack elementl-dev running..
I0527 19:44:29.016275 46303 eventsink.go:59] Trying to get account information via sts:GetCallerIdentity
I0527 19:44:29.016311 46303 eventsink.go:62] eventSink::Debug(<{%reset%}>Trying to get account information via sts:GetCallerIdentity<{%reset%}>)
I0527 19:44:29.080942 46303 eventsink.go:59] Trying to get account information via sts:GetCallerIdentity
pulumi:pulumi:Stack elementl-dev runningg
gentle-diamond-70147
05/28/2020, 4:48 PMAre you using temporary credentials?
You might try
pulumi config set aws:skipRequestingAccountId truepulumi config set aws:skipCredentialsValidation trueg
glamorous-printer-14057
05/28/2020, 5:05 PMhey @gentle-diamond-70147 thanks - no dice, I tried adding those - same behavior
glamorous-printer-14057
05/28/2020, 5:08 PMalthough I have the 2.x pulumi CLI, we are also on an ancient 0.x version of pulumi and pulumi-aws, which could be a factor? I’m not quite sure how we can safely incrementally move forward
glamorous-printer-14057
05/30/2020, 11:56 PMstrangely, it seems that downgrading node back to v10.17.0 has resolved this
pulumi up