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, I have Pulumi managing some EC2 instances, and I got an alert from AWS that one of them is unstable and is scheduled for replacement. What's the best way to deal with that? Would this work?

1. Manually terminate the instance in EC2 console
2. Run `pulumi refresh` to alert Pulumi that the instance is gone
3. Run `pulumi up` to get a new one


I do this sometimes :smile: not for EC2 but for K8S

Thanks :slightly_smiling_face: I have realised that maybe the even better answer to this is to setup an EKS Node Group so that (at least for EKS nodes) I don't need to `pulumi up` to get the right number of nodes

<https://www.pulumi.com/registry/packages/eks/api-docs/nodegroup/>