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

You can turn up logging (`-v=9 --logtostderr`), but if the problem is in the provider rather than Pulumi, then that won't help much.

Are you using time-based AWS credentials by any chance? I’ve seen this myself with session-based creds that expire before I run Pulumi.

i am but there should be about 22 hours left on it

i'll try a refresh anyways. just wasn't sure if there were some detailed logs somewhere that i could look at

Credentials are often an issue. Are you using an explicit Pulumi provider that uses non-default credentials? Are you assuming a role that requires MFA (and not using MFA)? Have you multiple sources of credentials defined at once, and Pulumi is picking up a different one than you think it should be?

ahh, turns out it just took a really long time to tell me that there was a dependency issue (seems object needed to be deleted and recreated because the description wasn't the same)

That's very fast when Pulumi knows about the must-delete rule. If it's slow,  it's probably your provider that is refusing to update. You can speed that up a lot by telling Pulumi that description is a cannot-update field. Onesec I'll get the docs...

<https://www.pulumi.com/docs/intro/concepts/resources/options/replaceonchanges/>

looking back the provider made that clear to me, it just didn't have enough information to know it would fail. surprised it didn't return more quickly but just didn't understand the error from AWS and was trying to retry some number of times.