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

Hi everyone. Loving pulumi :slightly_smiling_face:
On a `pulumi up` today I'm getting a non-ending run (at least 17m).
• logging with `v=9` didn't reveal anything
• tracing with `pulumi up --logtostderr -v=9 --tracing=file:./trace` then `PULUMI_DEBUG_COMMANDS=1 pulumi view-trace ./up.trace` shows:
    ◦ 17m in `pulumi plan`, which includes 17m in both `/pulumirpc.LanguageRuntime/Run` and `/pulumirpc.ResourceProvider/Configure`
is there a way to debug this further?
(for context, Win10 powershell (replicates with CMD), pulumi v3.14.0, making a single change on AWS.IAM, using hosted

Often when I see a hanging pulumi up it’s because one is using AWS credentials that have expired. Could this be the case here?

```var current = Output.Create(Aws.GetCallerIdentity.InvokeAsync());
var accountId = current.Apply(current =&gt; current.AccountId);```
and then add that to output of your stack. So your stack does nothing (no change) only read..

comment out any ops such  as your IAM change