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

Is there anything I can do to fix a `pulumi up` just spinning for 16 minutes? I feel like every other time when there's a bunch of updates to do, it just gets stuck? This is AWS

Have your AWS credentials maybe expired? (this happened to me before)

I've gotten corrupt stack states _because_ the credentials expired and then I had to export &amp; import to recover.

But it seems to me when one operation doesn't terminate it can hold up to around 20 minutes before giving up. Is there a way to control the timeout of this?

The operation that failed was to delete a security group in AWS, which couldn't be deleted because somebody had manually added a reference to it in another security group (or something, I don't speak AWS so I might be bsing here :joy:). So I had to manually remove this reference and then it passed without this long delay when running it the second time

But getting this error takes 20 minutes for some reason? :thinking_face: the error explaining something references the resource that isn't handled by Pulumi

Yes I had those long timeouts as well, when I tried deleting a `public-subnet` which had an `ENI` attached to it (that Lambda created dynamically). So I also had to do the manual removal of ENI and then `pulumi destroy`. It’s pretty annoying.

I see. So there's no way to actually just force an earlier timeout? :thinking_face:

No idea, let us know here if you find something