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

I'm setting up EC2 services over ECS using Auto Scaling Groups, there's this weirdest bug I can'g seem to solve, my pulumi up update is stuck on read aws:autoscaling:Group
Running the exact same code on another machine works perfectly somehow.
Anyone might know what can cause this? I have tried running destroy and then up again, I have tried pulumi refresh, I have even tried deleting and reinstalling pulumi on my machine, thanks.

The difference from machine to machine makes me think of authentication. Is reading the autoscaling group the first thing the program does? Or are there other AWS operations that succeed?

everything else succeed, the machine and credentials are the same that ran the first pulumi up for this stack
It looks like the whole operation is finished (including building the docker image and uploading it) yet the update is stuck (also no new logs written for more than a few minutes).
On another machine everything works fine.